Tilda Migration & Switching Guide 2026
Tilda has no importer, so pages are rebuilt with blocks, but same-domain wildcard 301s preserve old URLs. Full code export exists, gated to the Business plan.
Tilda Migration verdict
Migrating to Tilda is rebuild-in, export-out-if-you-pay.
There is no documented importer from another site or builder, so pages are recreated with Tilda blocks, and old URLs are preserved with same-domain 301 redirects that support /folder/* wildcards. The domain connects by transferring to Tilda's NS servers or adding A-records, with 3 to 24 hours to propagate.
Migrate to Tilda when you are rebuilding the design anyway and want strong on-page SEO, and put your site on the Business plan if a code-export exit matters to you. Map old URLs with same-domain wildcard 301s before the domain cutover, and accept the developer-ID backlink on lower tiers. If you need a one-click importer or a domain-to-domain redirect, plan that work outside Tilda.
- There is no documented site importer, so pages are a manual rebuild with blocks, with no WordPress or CSV import.
- Full code export is gated to the Business plan, so lower plans cannot export the site as code. A developer-ID backlink is embedded and removable only where the subscription plan allows.
- 301 redirects are same-domain with wildcards and no bulk CSV, and the domain connects via NS or A-records, avoiding wildcard A and CNAME.
- Site import
- None documented
- Code export
- Business plan only
- Attribution
- Developer-ID backlink
- Redirects
- Same-domain wildcards
- Domain
- NS or A-record
This page covers importing into Tilda and switching away. SEO output and pricing live on their own pages.
What moves into Tilda, and can you leave?
Pick what you are bringing to Tilda, and see exactly what transfers.
- URL redirects (301s): imports natively, Site Settings, SEO, 301 redirects; begin paths with /.
- Folder / wildcard redirects: imports natively, /blog/* same-domain wildcard.
- Custom domain: imports natively, NS transfer or A-record; avoid wildcard A / CNAME.
- Existing site (pages/content): manual rebuild, no importer; rebuild with blocks.
- WordPress / CSV bulk import: does not transfer, not documented.
- Cross-domain redirect: does not transfer, same-domain only.
- 1Rebuild pages with blocks, no importer.
- 2Re-enter per-page SEO, meta, slugs, canonical.
- 3Map same-domain wildcard 301s, no bulk CSV.
- 4Connect domain (NS or A-record), 3 to 24h propagation.
- 5(Exit) export .zip on Business plan, lower plans cannot export.
Every row is a documented import/export capability from Tilda and the source platforms, not an effort estimate.
Tilda migration configuration
In Site Settings, SEO, 301 redirects, enter each old path and its new path beginning with a slash and without the domain. Use a /folder/* wildcard to fold a whole section. Note redirects work within your current domain only, and no bulk-CSV import is documented, so large maps are entered by hand.
# Site Settings, SEO, 301 redirects (begin with /, no domain)
/about-us.html -> /about
/contact.php -> /contacts
# Wildcard: fold a whole old folder
/blog/* -> /articles/
# Same-domain only; no documented bulk-CSV import (manual entry).Connect a custom domain by adding the A-record IP that Tilda shows in Site Settings, Domain, or by transferring the domain to Tilda's NS servers (which assigns IPs automatically). Avoid wildcard A-records and CNAMEs. Propagation takes 3 to 24 hours.
; Method A, A-record (value shown in Site Settings, Domain):
@ A <IP shown by Tilda>
; Method B, transfer to Tilda NS servers (Tilda manages records, auto IP).
; Avoid wildcard A-records and CNAME records.
; Propagation: 3 to 24 hours.On the Business plan, export the whole site as a .zip from Site Settings, Export, then upload the unzipped files to your own server over FTP. On lower plans this export is unavailable and a developer-ID backlink stays embedded, so factor the plan tier into your exit plan.
# Site Settings, Export, Download as .zip (Business plan only)
unzip tilda-export.zip -d ./my-site
# Upload ./my-site to your server via FTP.
# Lower plans: no code export, and the developer-ID backlink stays embedded.What moves when you migrate to Tilda
| Migration element | On Tilda | Detail | Source |
|---|---|---|---|
| Existing site import | Not documented | No importer from WordPress or another builder; rebuild pages with blocks / Zero Block | — |
| Full code export (out) | Business plan only | Everything made on Tilda can be exported to your server, but only on the Business plan | — |
| Export method | .zip over FTP | Site Settings, Export, Download as .zip, then upload the unzipped files to your server via FTP | — |
| Developer-ID backlink | Embedded (plan-gated removal) | An ownership backlink block is affixed; deleting it is forbidden except where a subscription plan allows | — |
| 301 redirects | Same-domain wildcards | Map old URLs to new with /blog/* wildcards; same-domain only, no bulk CSV documented | — |
| Custom domain | NS or A-record | Transfer to Tilda NS-servers (auto IP) or add A-records yourself; avoid wildcard/CNAME | — |
Source-to-Tilda mapping
| Old-site element | Lands on Tilda as | Caveat | Source |
|---|---|---|---|
| A single old URL | A 301 redirect | Site Settings, SEO, 301 redirects; begin paths with / | — |
| A whole old folder | One wildcard 301 (/blog/*) | Same-domain only; a domain-to-domain move is not covered | — |
| Pages and layout | Rebuilt with blocks / Zero Block | No importer; this is the bulk of the work | — |
| Per-page meta & canonical | Re-entered in SEO settings | Canonical auto-sets on the connected domain; editable per page | — |
| The site as code (out) | .zip export to your server | Business plan only; lower plans cannot export | — |
| Your domain | NS transfer or A-records | 3 to 24 hours to propagate; avoid wildcard A / CNAME | — |
Tilda migration timeline and rollout
| Phase | What happens | Effort | Source |
|---|---|---|---|
| 1. Rebuild pages | Recreate with blocks / Zero Block | High, no importer | — |
| 2. Re-enter SEO | Per-page meta, slugs, canonical | Medium, granular but point-and-click | — |
| 3. Redirect map | Same-domain wildcard 301s | Low to medium, manual entry, no bulk CSV | — |
| 4. Connect domain | NS transfer or A-records | Low, 3 to 24h propagation | — |
| 5. (Exit option) Export code | .zip over FTP | Low, Business plan only | — |
What to verify before you commit to Tilda
- There is no site importer, so pages are a manual rebuild with blocks; budget that time rather than expecting a WordPress or CSV import
- The exit is plan-gated: full code export to your own server is available only on the Business plan, so lower plans cannot take the site out as code
- A developer-ID backlink is embedded and may not be removed except where your subscription allows, so the platform attribution is part of the deal on lower tiers
- Redirects are same-domain only with no documented bulk CSV, so a domain-to-domain move or a very large URL map needs hand work or your old host
Tilda Migration FAQ
Can I import an existing website into Tilda?
Not through a documented importer. Tilda's help center describes building pages with blocks and Zero Block, but there is no WordPress, other-builder or CSV site importer, so an inbound migration is a manual rebuild. What Tilda gives you for the move is its redirect system, so your old URLs keep resolving to the new pages once you map them.
Can I export my Tilda site as code?
Yes, but only on the Business plan. You export the whole site as a .zip from Site Settings, Export, then upload the unzipped files to your own server over FTP. On lower plans the code export is unavailable, and a developer-ID backlink stays embedded in the site. So if a clean code exit matters to you, factor the Business-plan tier into the decision.
How do Tilda redirects work for migration?
In Site Settings, SEO, 301 redirects, you enter each old path and its new path beginning with a slash and without the domain. You can use a /folder/* wildcard to fold a whole section. The limits are that redirects work within your current domain only, and there is no documented bulk-CSV import. So a domain-to-domain move or a very large URL map is hand-entered or handled at your old host.
How do I connect my domain to Tilda?
Two ways. You can transfer the domain to Tilda's NS servers, in which case Tilda manages the records and assigns IPs automatically. Or you can add the A-record IP that Tilda shows in Site Settings, Domain at your own registrar. Avoid wildcard A-records and CNAMEs, and allow 3 to 24 hours for changes to propagate.
What is the catch with leaving Tilda?
Two things. The full code export that lets you take the site to your own server is gated to the Business plan, so lower-tier sites cannot leave as code. And a developer-ID backlink is embedded by default and may only be removed where your subscription plan allows. Neither blocks you, but both mean the clean exit depends on your plan tier, so choose it with the exit in mind.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Tilda Official | Official product page | July 10, 2026 |
| Tilda Support | Search Engine | July 10, 2026 |
| Tilda Support | Export | July 10, 2026 |
| Tilda Support | Customdomain | July 10, 2026 |
Every fact on this Tilda 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 Tilda
Every page on Tilda 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