Jimdo to Tilda Migration: A Complete Technical Guide

Jimdo to Tilda Migration: A Complete Technical Guide

Migrating from Jimdo to Tilda has no automated path. Neither platform offers a direct transfer tool, and Jimdo does not provide a comprehensive export function for website content. Jimdo's own help center confirms that there is no option for creating a backup of your website yourself. On the Tilda side, the constraint is equally hard: there is no automatic way to transfer a website from another platform — you rebuild manually in Tilda's editor.

As with a Wix to Webflow migration, every Jimdo-to-Tilda migration is a manual rebuild with a structured content extraction phase up front. This guide covers auditing your existing site, extracting content and assets, rebuilding in Tilda's block editor, importing product data, preserving SEO, transferring your domain, and launching without breaking anything.

Decide Your Approach Before You Start

Use this matrix to scope the project before touching any tools:

Labor estimates assume one experienced operator. Add 30–50% if the person building in Tilda is learning the platform simultaneously. The 5,000-product ceiling in Tilda's built-in catalog is a hard cutoff — stores above that limit need a different target platform regardless of team size.

Identify Which Jimdo Product You Have

Before scoping anything, confirm whether you're running Jimdo Creator or Jimdo Website Builder. You can tell by the editor URL and dashboard pattern: Creator uses cms.e.jimdo.com and subdomains like jimdoweb.com or jimdofree.com; Website Builder uses builder.e.jimdo.com and jimdosite.com. Jimdo documents the distinction in their help center.

This matters for migration planning:

• Jimdo Creator can contain custom HTML, CSS, JavaScript, head code, widget elements, and custom templates. Business logic may be buried in Widget/HTML elements, Edit Head, and custom template areas. These need a deeper audit.
• Jimdo Website Builder does not support custom code, iframes, or external widgets. Lower code risk, but you still need to capture page content, forms, products, and SEO metadata.

Jimdo plan tier also affects what you can access before cancellation:

If your account has been downgraded to Free (intentionally or by expiry), form archives and order history may already be inaccessible. Check this before doing anything else.

The usual reason behind a Jimdo-to-Tilda move is design control. Jimdo operates as a managed, closed-ecosystem builder optimized for getting a site up fast. Tilda caters to teams that need granular control over typography, animations, and grid layouts — particularly through its Zero Block engine.

What Moves and What Doesn't

Set expectations before you start extracting:

• Text, images, PDFs, and navigation move cleanly, but you need your own capture process. Jimdo Creator has no self-service backup, and the suggested browser-extension workaround saves one page at a time.
• Blog content has a workable path. Jimdo Creator exposes a blog RSS feed at /rss/blog/, which you can parse and recreate in Tilda's Feed system.
• Product catalogs move best through Tilda's CSV/YML import. Tilda accepts HTTPS image URLs and uses fields like External ID and Parent UID for updates and variants.
• Historical leads and orders must be exported before shutdown. Jimdo Creator form archives can be downloaded as CSV, and archived messages are deleted after six months.
• Structured data and embeds need to be recreated. Jimdo documents rich snippets as a custom-programming task; Tilda supports JSON-LD via the page head.
• Order history, customer accounts, and transaction records do not transfer to any other platform. Archive these separately before canceling Jimdo.

The practical takeaway: Tilda is a better target than Jimdo is a source. Tilda has structured import paths for feeds and catalogs, but the source side still requires manual collection or custom extraction.

Audit and Inventory Your Jimdo Site

Because Jimdo Creator does not provide a self-service backup, the audit is not overhead — it is your recovery plan. Do it before anyone starts building pages in Tilda.

Open every page of your Jimdo site and document:

• Pages and URL paths — record the full URL of every page (e.g., yoursite.com/about, yoursite.com/services/consulting)
• Text content — headlines, body copy, CTAs
• Images and media — file names, alt text, which page each appears on
• Blog posts — titles, dates, categories, body content
• E-commerce products — names, descriptions, prices, images, variants, SKUs
• Forms — field names, destinations (email, CRM integration)
• SEO metadata — page titles, meta descriptions, canonical tags, robot directives
• Third-party integrations — analytics, chat widgets, email marketing embeds
• Custom code (Creator only) — HTML in text elements, Widget/HTML elements, Edit Head, and custom template areas

Use a spreadsheet. This inventory becomes your migration checklist, QA document, and redirect map.

Working Inventory Format

old_url,page_type,new_url,status,redirect_type,owner,notes
/about,standard,/about,ready,301,marketing,keep slug
/blog/post-1,blog,/articles/post-1,ready,301,content,move to Tilda Feed
/files/pricing.pdf,asset,/files/pricing.pdf,ready,200,ops,update CTA links
/contact,form,/contact,qa,301,ops,map to Tilda webhook

Every old URL should end in one of three states: recreated, 301 redirected, or intentionally removed with a real 404 or 410. Google recommends preparing a URL mapping before the move and replacing internal links on the new site with final URLs instead of leaning on redirect chains.

Extract Content from Jimdo

This is the most labor-intensive phase. Jimdo gives you almost nothing for free.

Text and Page Content

For small sites (under 20 pages), the most reliable method is copying text directly from each page into a document or spreadsheet. Log into your Jimdo account, create a document for each page, copy and paste all text content, save all images and media files, and take screenshots of your layout for reference.

For larger sites, a programmatic scraping approach reduces error rates. Jimdo wraps content in predictable div classes — text blocks typically live within .j-module or .cc-m-richtext containers.

import requests
from bs4 import BeautifulSoup
import time
 
def scrape_jimdo_page(url):
    try:
        response = requests.get(url, timeout=10)
        response.raise_for_status()
    except requests.RequestException as e:
        print(f"Failed to fetch {url}: {e}")
        return None
 
    soup = BeautifulSoup(response.text, 'html.parser')
    title = soup.title.string if soup.title else 'No Title'
    content_blocks = soup.find_all('div', class_='j-module')
    page_text = [block.get_text(strip=True) for block in content_blocks]
 
    return {
        'url': url,
        'title': title,
        'content': ' '.join(page_text)
    }
 
def scrape_site(urls, delay=2):
    results = []
    for url in urls:
        result = scrape_jimdo_page(url)
        if result:
            results.append(result)
        time.sleep(delay)  # Avoid rate limiting
    return results
 
# Usage: pass your full URL list from the inventory spreadsheet
urls = [
    "https://yoursite.com/about",
    "https://yoursite.com/services",
    # ... add all URLs from your inventory
]
scraped = scrape_site(urls)

The delay=2 argument spaces requests two seconds apart. Jimdo's CDN will rate-limit aggressive scrapers. Increase the delay if you see 429 responses.

Images and Media Files

Images hosted on Jimdo's CDN (image.jimcdn.com) will break once your subscription ends. Right-click and save every image, or use a browser extension like DownThemAll or a site mirroring tool like HTTrack to bulk-download assets. Organize downloaded images into folders matching your page structure and keep original filenames.

Create a mapping spreadsheet with:

• Original Jimdo URL
• Local file path
• Alt text (extracted from the Jimdo DOM)
• Target Tilda page/block

Blog Posts via RSS

If you have a Jimdo blog, access posts through the RSS feed. The typical URL:

https://yourdomain.com/rss/blog

Open this URL in a browser, save the XML file, and parse it. The RSS feed includes post titles, publication dates, and body content (usually as HTML snippets). Featured images won't appear at full resolution — download those separately.

Operational Data

Download Creator form archives as CSV before cancellation or downgrade — once the site falls to the free tier, the archive may no longer be accessible. Export Website Builder orders if the business needs them for support or accounting after launch.

Rebuild Your Site in Tilda

Tilda uses a block-based page builder — you assemble pages from pre-designed, customizable sections. Tilda provides 550+ blocks covering menus, about pages, features, pricing, contact sections, and more.

Choose the Right Tilda Building Block

• Standard blocks for service pages, about pages, landing pages, and other mostly static marketing content. Responsive by default and fast to implement.
• Zero Block for custom positioning, animations, or layouts that standard blocks can't handle. Tilda documents Figma import into Zero Block via API token.
• Feeds for blog, news, or event archives. Feed posts get their own URLs and create feed-specific sitemap files.
• Product Catalog for anything beyond a handful of SKUs — supports up to 5,000 items.

Zero Block Mobile Breakpoints

Zero Block is Tilda's most powerful feature and its most common source of mobile layout failures. Unlike standard blocks, Zero Block elements do not auto-stack or reflow on smaller screens. You must manually adjust layout, font sizes, and positioning across all five responsive breakpoints for every Zero Block you create:

Common Zero Block mobile failure patterns:

• Text elements set to absolute pixel positions overflow their containers on narrow screens
• Multi-column layouts that aren't restructured at breakpoints 4 and 5 render as overlapping columns on phones
• Font sizes set only at Desktop breakpoint appear identical (too large) at Mobile Portrait
• Background images not adjusted per breakpoint show cropped or wrong-aspect-ratio on mobile

Work through breakpoints from Desktop down to Mobile Portrait. The most common shortcut that breaks sites: building only the Desktop layout and assuming it will adapt. It will not.

Tilda Plan Comparison

Custom domain access, product catalog limits, and Zero Block availability depend on your Tilda plan. See Tilda's current pricing page for the latest rates, as these change periodically.

If you have an active Jimdo store requiring payment processing on Tilda, you need the Business plan. The Personal plan supports product display and lead capture but not transactional checkout.

Global Settings First

Before building individual pages, establish global parameters:

1. Typography — Upload custom web fonts or connect Google Fonts/Adobe Fonts in Site Settings > Fonts and Colors.
2. Header and Footer — Build these as separate pages in Tilda, then assign them globally in Site Settings > Header and Footer.
3. Forms and integrations — Tilda forms send data to email, Google Sheets, CRMs, or a custom webhook. Tilda webhooks require HTTPS, expect a response within five seconds, and only retry twice at one-minute intervals. Test your receiver before the design work is done.

Page-by-Page Reconstruction

Work from your inventory spreadsheet. For each Jimdo page:

1. Create a new page in your Tilda project
2. Set the page URL slug to match the old Jimdo path
3. Select blocks that approximate the original layout
4. Paste in text content
5. Upload images and set alt text
6. Configure page SEO settings (title, description, Open Graph image)

Blog Setup with Feeds

Tilda handles blog functionality through its Feed feature. Create a blog page, add a feed block, and enter each blog post. Copy the title, date, content, and featured image from the RSS data you extracted. Tilda Feed posts use a /tpost/ URL prefix by default — for example, a post titled "How We Work" becomes /tpost/how-we-work. This structure is not configurable. Because Jimdo blog URLs do not follow this pattern, 301 redirects are mandatory for every blog post without exception.

E-commerce Product Import

Tilda's Product Catalog accepts CSV and YML file imports for bulk product handling.

Jimdo does not provide a structured product export tool. You'll need to manually compile product data into a spreadsheet and format it to match Tilda's expected schema:

If your Jimdo store exceeds 5,000 products, Tilda's built-in catalog is not a viable target. Evaluate Shopify, WooCommerce, or another dedicated e-commerce platform instead.

SEO Preservation and 301 Redirects

This is the step most people skip — and it's the one that destroys search rankings.

Extract the Current Sitemap

Locate your Jimdo sitemap at yourdomain.com/sitemap.xml. Download it — this contains every indexable URL and becomes your master redirect checklist.

Before any migration work begins, pull a Google Search Console report on your highest-traffic pages. Sort by clicks over the trailing 90 days. Any page with more than ~50 monthly organic clicks is a high-risk URL — a missing redirect on these pages has direct, measurable revenue impact. Export this report and merge it with your sitemap to prioritize which redirects get QA'd first.

Configure 301 Redirects

For URLs that must change, set up 301 redirects in Tilda under Site Settings → SEO → 301 Redirects. Tilda supports path-based 301 rules within the same domain and wildcard redirects using the * symbol.

Tilda redirect rule syntax:

/old-path/ → /new-path/
/blog/* → /articles/*
/services/old-name/ → /services/new-name/

The wildcard * matches the remainder of the path and passes it to the destination. Use this to redirect entire directory structures in a single rule. For example, /blog/* → /articles/* redirects /blog/post-title to /articles/post-title without creating one rule per post — useful for section renames where slugs remain identical.

However, because Tilda Feed URLs follow a /tpost/ structure, you cannot use a wildcard to redirect Jimdo blog posts to Tilda Feed posts. You must create one redirect rule per blog post.

Pay special attention to:

• Pages with high organic traffic (check Google Search Console before migration)
• Pages with external backlinks
• Blog post URLs — requires one rule per post
• Product page URLs

Google's site-move guidance recommends server-side permanent redirects, avoiding redirect chains, submitting the new sitemap, and keeping redirects in place for at least a year.

What to Expect After Launch

Some ranking fluctuation is normal during any site migration. Typical recovery timeline:

• Week 1–2: Googlebot discovers and begins processing the new sitemap; initial 404 errors appear in Search Console as Googlebot revisits old URLs before redirects are indexed
• Week 2–4: Redirect chains are resolved; Search Console coverage errors peak, then decline if redirects are correctly configured
• Week 4–8: Rankings stabilize for most pages; pages with strong backlink profiles recover first
• Week 8–16: Long-tail and lower-authority pages return to pre-migration positions (if redirects are in place)

Metrics to monitor in Google Search Console post-launch:

1. Coverage report → Not Found (404) — any spike here indicates missing redirects; investigate immediately
2. Coverage report → Redirect Error — indicates malformed or chained redirects
3. Performance report → Clicks/Impressions by page — compare pre- and post-launch traffic for your top 20 pages weekly
4. Sitemaps — confirm the new sitemap is indexed; remove the old sitemap entry if it still exists

If 404 errors spike in week one and don't resolve by week three, you have redirect gaps. Identify the URLs from the Search Console Not Found report, cross-reference with your inventory spreadsheet, and add the missing rules.

Metadata Transfer

For every page in Tilda, open Page Settings > SEO and set:

• Title tag (under 60 characters)
• Meta description (under 160 characters)
• Open Graph image for social sharing
• Any structured data (JSON-LD) via the page head — schema markup from Jimdo does not carry over automatically

Domain Transfer and DNS Cutover

Domain transfer is a two-part process: getting the domain away from Jimdo, and pointing it at Tilda.

Get Your AuthCode from Jimdo

If you want to move your domain from Jimdo to another provider, you need an AuthCode (also called an EPP code). To request it:

1. Log into your Jimdo dashboard
2. Go to Domains settings
3. Click your domain → Request Transfer Code
4. The AuthCode will be emailed to the AdminC address (the email used during domain registration)

For .com, .net, .org, and .info domains, the AuthCode is valid for 60 days. Country-code TLDs (.co.uk, .de, .fr, etc.) have different transfer rules — verify with the relevant registry before initiating.

We recommend transferring the domain to a dedicated registrar (Cloudflare, Namecheap, etc.) to decouple domain ownership from your website builder.

Point Your Domain to Tilda

Tilda does not act as a domain registrar — you connect your domain via DNS records. Two options:

Option A: A-Record Method Add two A-type records pointing to Tilda's IP address — one for the root domain (@) and one for www. Always verify the current IP in your Tilda domain settings before configuring — Tilda's IP addresses are subject to change. Use this method if you have other services on the domain (email hosting, subdomains pointing elsewhere).

Option B: Nameserver Delegation Add Tilda's NS records: ns1.tildadns.com and ns2.tildadns.com. Simpler if Tilda is your only web property on that domain. Note that delegating nameservers gives Tilda control over all DNS records for the domain — including MX records for email. If you have existing email on the domain, use Option A instead.

In Tilda, go to Site Settings → Domain, enter your domain name, and save. DNS propagation takes up to 24 hours, though most updates resolve within 1–2 hours. Do not cancel your Jimdo subscription until propagation is complete and verified.

Multilingual Sites

Multilingual Jimdo sites represent one of the highest-complexity migration scenarios. Jimdo Creator does not have a native multilingual system — multilingual sites on Creator are typically built as separate page trees (e.g., /en/, /de/, /fr/ directories) with manual navigation linking between them.

Tilda also does not have a built-in multilingual or translation management system. Your options on Tilda:

• Separate Tilda projects per language — most common approach. Each language gets its own Tilda project, connected to a subdomain or subdirectory. Requires separate SEO configuration, redirect maps, and domain setup per language.
• Single project with language-segmented pages — manageable for small multilingual sites (2 languages, ≤20 pages each). Does not support hreflang tags natively; you must inject them manually via page head code.
• Third-party translation overlay (Weglot, etc.) — adds automatic translation and hreflang management on top of a single Tilda project. Introduces a dependency and monthly cost but significantly reduces build time for 3+ language sites.

For each language, you need a separate redirect map, a separate sitemap submitted to Search Console, and correctly implemented hreflang attributes pointing between language variants. Missing hreflang implementation after migration is the most common SEO error in multilingual moves.

Pre-Launch QA Checklist

Before switching your domain, verify everything:

• All pages from your inventory are rebuilt in Tilda
• Text content matches the original (check for copy-paste formatting issues)
• All images load correctly with proper alt text
• Blog posts have correct dates and content
• Product catalog imports are complete with correct pricing
• Forms submit successfully and data reaches the intended destination
• SEO metadata (title tags, meta descriptions) is set on every page
• Structured data (JSON-LD) is re-implemented and validated with Google's Rich Results Test
• 301 redirects are configured for every changed URL, including one rule per blog post
• Mobile responsiveness is verified across all five Zero Block breakpoints where applicable
• Analytics tracking is installed and firing correctly (verify with real-time report)
• SSL certificate is active (Tilda provides free SSL on paid plans)
• Staging noindex or password protection is ready to be removed
• New sitemap is generated and ready for Google Search Console submission
• Hreflang tags implemented (multilingual sites only)
• Email mailboxes recreated with new provider before domain transfer

After launch: submit the new sitemap in Search Console within 24 hours, and monitor the four metrics listed in the SEO section above weekly for the first eight weeks. For pages you intentionally drop, return a real 404 or 410 — Tilda lets you assign a custom 404 page in Site Settings.

Common Failure Modes

Underestimating content volume. A 20-page Jimdo site with a blog and product catalog can take 20–40 hours of manual work. The decision matrix at the top of this guide provides more granular estimates.

The semicolon delimiter. Tilda uses semicolons in CSV imports, not commas. This single detail breaks more product imports than anything else.

Orphaned blog posts. Tilda Feeds use a fixed /tpost/ URL prefix. You cannot match Jimdo blog slugs. One redirect rule per post is not optional.

Losing SEO equity. Missing redirects on high-traffic pages have direct traffic impact within days of launch. Pull your Search Console data before migration — any page above 50 monthly organic clicks needs a verified redirect in place before DNS cutover.

Forgetting email migration. Jimdo email accounts don't survive domain transfers. If you used you@yourdomain.com on Jimdo, set up equivalent mailboxes with a third-party provider before the switch.

Tilda's product limit. The built-in Product Catalog supports up to 5,000 items (Business plan). Stores above this threshold need a different e-commerce platform.

Zero Block breakpoint failures. Building only the Desktop Zero Block layout and assuming it adapts is the fastest way to break mobile. Work through all five breakpoints explicitly.

Jimdo domain lock-in. Jimdo-hosted domains cannot be redirected externally and don't expose custom DNS settings. Resolve domain ownership before launch week.

Nameserver delegation breaking email. If you switch to Tilda's nameservers (ns1.tildadns.com / ns2.tildadns.com) while active email is running on the domain, your MX records will be wiped. Use the A-record method if email is in play.

Skipping the plan comparison. Attempting to run e-commerce on Tilda Personal (no payment processing) or expecting Zero Block on Tilda Free are both plan-level mismatches that halt the project mid-build.

This is the friction point ClonePartner eliminates. We build custom extraction scripts, handle schema mapping, QA every redirect, and sequence the launch so your business keeps collecting leads and preserving URLs while the migration happens.