Jimdo Creator and Jimdo Website Builder (Dolphin)
Move your Jimdo website to Staticbot
Bring your available Jimdo content, originals and saved files to Staticbot. Upload one archive or use Git; our team will help review what is needed to prepare the website.
Platform instructions checked October 16, 2026. Controls and plan availability can change.
Content recovery · rebuild required
What you can bring across
Your own text, original assets and a page inventory. A saved browser page can be a reference, but is not a verified, complete deployment package.
Bring the files you have in one ZIP, or use your existing Git repository. Staticbot will inspect the inputs and request a review. You do not need to rebuild the website before submitting it.
Before you start
- Access to the Jimdo site and knowledge of whether it uses Creator or Website Builder (Dolphin). Their help instructions differ.
- Original images and files, a list of URLs, and an inventory of forms, shop features and account-dependent content.
Bring the files you already have
Identify Creator or Website Builder
Include which Jimdo product you use if you know it. Creator and Website Builder (Dolphin) have different backup guidance. Neither documented route supplies a portable self-service website package.
Gather available exports and originals
Include your existing saved pages, archives, original images, downloads and page text. Add the Jimdo URL and a note about anything missing. Do not rebuild pages or convert saved files to a new project first.
Include page references if you already have them
Creator documentation describes saving individual pages with Fireshot or SingleFile. Existing captures can help with review, but they do not prove that every linked file or hosted service is portable. You do not have to create a finished website from them yourself.
Add notes and create one package
Include a short description of the forms, shop and other features you need. ZIP the available material together, or commit it to your existing Git repository. Domain transfer codes are separate and do not belong in the package.
Bring the files to Staticbot
Use Upload your project or the Git import form. Staticbot inventories the inputs and requests a review, including the originating website scan when available. We will help decide how to recover missing material and prepare the replacement website.
Features to review before moving
- Neither documented backup route supplies the self-service portable website archive needed for a direct transfer.
- A browser-saved homepage does not recover the complete site or make Jimdo-hosted services independent.
- If the old site is already inaccessible, recovery depends on the owner’s originals, existing archives and what Jimdo support can provide.
Check the preview before changing DNS
Compare the new site against your page inventory, test downloadable files and form delivery, and check mobile layouts. Recreate old URL paths or arrange and test redirects for changed ones.
Keep the old account and your backups until the replacement works. You can connect a custom domain you control after testing; the provider’s own subdomain stays with the original platform.
Next: bring your files to Staticbot
Choose the separate ZIP upload or Git import form. Staticbot keeps the package and its inventory for review. Once the website is prepared, the existing hosting guides explain previewing and deployment.
Upload or import your files