
Carrd Migration & Switching Guide 2026
Carrd has no importer, so a site is rebuilt as one page, but wildcard redirects preserve old URLs on Pro. The Pro code download is a one-way static snapshot.
Carrd Migration verdict
Carrd migration is light in, one-way out.
There is no importer, so an existing site is rebuilt as a single Carrd page. But you preserve old URLs with /request=destination redirects on Pro with your own domain, including wildcards that fold whole paths.
Migrate to Carrd when you are consolidating onto a simple one-page site and your continuity need is preserving a handful of URLs. Put the site on Pro so you get redirects and a custom domain. Do not count on a clean code exit, since the download is a one-way static snapshot whose forms break. If you move between Carrd accounts, use the native transfer or clone instead, which keeps the site working.
- There is no site importer, so an existing multi-page site is rebuilt as one Carrd page, and the migration tool is URL-preserving redirects.
- The code export is one-way, since forms and platform elements break and the download cannot be re-uploaded to Carrd. Redirects and a custom domain require Pro and your own domain, so free .carrd.co sites cannot preserve URLs or use a custom brand.
- Between Carrd accounts, use the native transfer or clone, which keeps the site functional, rather than the static download.
- Site import
- None (rebuild one page)
- URL preservation
- Redirects + wildcards (Pro)
- Code export
- One-way (forms break)
- Domain
- A + www CNAME, ~1h
- Between accounts
- Native transfer / clone
This page covers importing into Carrd and switching away. SEO output and pricing live on their own pages.
What moves into Carrd, and can you leave?
Pick what you are bringing to Carrd, and see exactly what transfers.
- URL redirects (/request=destination): imports natively, Pro + own domain; preserve old URLs.
- Wildcard redirects: imports natively, /products/* or /blog/* with substitution.
- Custom domain + SSL: imports natively, A record + www CNAME; free Let's Encrypt (Pro).
- Existing multi-page site: manual rebuild, no importer; rebuild as one page.
- WordPress / CSV bulk import: does not transfer, not documented.
- 1Rebuild as one page with sections, no importer.
- 2Map /request=destination redirects, Pro + own domain.
- 3Connect domain (A + www CNAME), ~1h init.
- 4Enable SSL (Let's Encrypt), free.
- 5(Exit) download code, one-way, forms break, no re-upload.
Every row is a documented import/export capability from Carrd and the source platforms, not an effort estimate.
Carrd migration configuration
On Pro with your own domain, preserve old URLs by entering /request=destination pairs, one per line. Point to a section anchor, an external URL or the site, and use wildcards to fold whole paths. This is Carrd's main migration tool.
# Redirects (Pro, Use my own domain): /request=destination
/about.html=/ # old page back to the site
/contact=#contact # to a section anchor
/products/*=#products # wildcard to a section
/blog/*=https://domain.ext/blog/* # wildcard, * substituted into the target
/*=/ # catch-all back to the siteConnect a custom domain (Pro) with an A record for @ to the IP Carrd shows, plus a www CNAME to the bare domain. www and apex auto-forward to each other. The domain initializes in up to an hour, then enable free Let's Encrypt SSL.
@ A <IP shown by Carrd>
www CNAME domain.ext ; www <-> apex auto-forward
; Initialization: up to ~1 hour (usually faster).
; Then enable SSL (Let's Encrypt, free).On Pro you can download the unminified source as a .zip. Know the limits: form and other platform-dependent elements are present but non-functional in the download, and it cannot be re-uploaded to Carrd. It is a one-way static snapshot, not a portable round-trip.
# Pro: download unminified source as .zip (one-way)
unzip carrd-export.zip -d ./my-site
# Caveats:
# - form / platform elements are present but NON-functional
# - the download CANNOT be re-uploaded to CarrdWhat moves when you migrate to Carrd
| Migration element | On Carrd | Detail | Source |
|---|---|---|---|
| Existing site import | Not documented | No importer from WordPress or another builder; rebuild the single page | — |
| URL preservation | Redirects (Pro) | Preserve old URLs with /request=destination redirects when moving an existing site to Carrd | — |
| Code export (out) | One-way (Pro) | Download unminified source, but form/platform elements break and it cannot be re-uploaded | — |
| Site transfer / cloning | Native | Transfer a site between Carrd accounts, and clone sites within the platform | — |
| Custom domain | A + CNAME (Pro) | An A record for @ to the shown IP and a www CNAME to the bare domain; auto www/apex forward | — |
| SSL | Free (Let's Encrypt) | Free HTTPS via Let's Encrypt after the domain initializes | — |
Source-to-Carrd mapping
| Old-site element | Lands on Carrd as | Caveat | Source |
|---|---|---|---|
| A multi-page old site | One page with sections | No importer; rebuild, this is Carrd's single-page model | — |
| An old URL | A /request=destination redirect | Point to a section, external URL or the site; Pro + own domain | — |
| A whole old path | One wildcard redirect | /products/*=#products or /blog/*=https://domain.ext/blog/* | — |
| The site as code (out) | One-way static .zip | Forms/platform elements break; cannot be re-uploaded to Carrd | — |
| Your domain | A record + www CNAME | Init takes up to an hour; www/apex auto-forward | — |
| A site between accounts | Native transfer / clone | Move ownership without rebuilding | — |
Carrd migration timeline and rollout
| Phase | What happens | Effort | Source |
|---|---|---|---|
| 1. Rebuild the page | Recreate as one page with sections | Low to medium, single page, no importer | — |
| 2. Map redirects | /request=destination, with wildcards | Low, Pro + own domain | — |
| 3. Connect domain | A record + www CNAME | Low, init up to an hour | — |
| 4. Enable SSL | Let's Encrypt, free | Low, after domain initializes | — |
| 5. (Exit option) Download code | One-way static .zip | Low, but forms break and no re-upload | — |
What to verify before you commit to Carrd
- The exit is one-way: you can download unminified source on Pro, but forms and platform elements break and the download cannot be re-uploaded, so treat leaving as a static snapshot, not a portable move
- There is no site importer, so an existing multi-page site is rebuilt as one Carrd page; the migration tool you get is URL-preserving redirects, not content import
- Redirects and the custom domain require Pro and your own domain, so a free or .carrd.co site cannot preserve URLs or run on your brand, price the tier in
- Between Carrd accounts, prefer the native transfer or clone rather than the code download, since transfer keeps the site fully functional while the download does not
Carrd Migration FAQ
Can I import an existing website into Carrd?
Not through an importer. Carrd has no WordPress, other-builder or CSV import, so an existing site is rebuilt as a single Carrd page. What Carrd gives you for the move is redirects. On Pro with your own domain you preserve old URLs by mapping them to sections, external URLs or the site, including wildcards. Carrd explicitly frames this as useful when moving a site in.
Can I export my Carrd site?
Yes on Pro, but it is one-way. You can download the unminified source as a .zip, however form and other platform-dependent elements are present but non-functional in the download, and crucially the download cannot be re-uploaded to Carrd. So the export is a static snapshot you can host elsewhere, not a portable round-trip, and the interactive parts of the site do not survive it.
How do Carrd redirects work for migration?
On Pro with your own domain, you enter /request=destination pairs, one per line. A request like /about.html can point back to the site, /contact can point to a section anchor, and /blog can point to an external URL. Wildcards fold whole paths, for example /products/*=#products, with the matched portion substituted into the target. A /*=/ rule catches everything back to the site.
How do I connect my domain to Carrd?
On Pro, add an A record pointing @ to the IP address Carrd shows, plus a www CNAME pointing back to the bare domain. The www and the apex auto-forward to each other. The domain then initializes automatically, which can take up to an hour but is usually faster, after which you enable free SSL via Let's Encrypt. The domain must be registered before you connect it.
What is the catch with leaving Carrd?
The exit is one-way. The downloadable source is unminified static HTML, CSS and JS, but the forms and any platform-dependent elements stop working, and you cannot upload the download back into Carrd. If you are simply moving a site between Carrd accounts, use the native transfer or clone instead, which keeps the site fully functional, rather than the lossy code download.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Carrd Official | Official product page | July 10, 2026 |
| Carrd Sites Downloading | Sites Downloading | July 10, 2026 |
| Carrd Sites Setting Up A Sitemap | Sites Setting Up A Sitemap | July 10, 2026 |
| Carrd Sites Setting Up Redirects | Sites Setting Up Redirects | July 10, 2026 |
| Carrd Sites Setting Up Ssl | Sites Setting Up SSL | July 10, 2026 |
| Carrd Sites Transferring | Sites Transferring | July 10, 2026 |
| Carrd Sites Using A Custom Domain | Sites Using A Custom Domain | July 10, 2026 |
Every fact on this Carrd page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.
Explore Carrd
Every page on Carrd in one place, you are on migration.
Snapshot, score and verdict
You are here
SEO output and page performance of sites it builds
Every tier and the entry price
Compared and ranked vs peers
Price and feature change history
Browse the full Website Builders category
