Elementor Migration Checklist: 15 Steps Before You Go Live

Moving an Elementor site is more than copying files. Page data, global styles, fonts, and saved addresses all need attention. This Elementor migration checklist gives you 15 steps to follow before, during, and after the move, so nothing breaks on launch day.

Print it, copy it into your project tool, and tick each item as you go.

Before the move: prepare

1. List what you have. Write down your WordPress, Elementor, and PHP versions, plus every active plugin. You want the same setup on the new server.
2. Take a full backup. Files and database, stored somewhere outside the server. Test that you can open it.
3. Update everything first. Update WordPress, Elementor, and your plugins on the old site. It is easier to find issues there than after the move.
4. Clear caches and remove junk. Delete unused plugins, empty the trash, and clear page caches so you do not copy old files.
5. Export your key design assets. Save your templates, popups, and global settings as extra backup files from the Elementor templates screen.

During the move: copy and connect

1. Copy the files and database. Use your host’s migration tool, a migration plugin, or a manual copy. Our FTP and SFTP guide helps with the manual route.
2. Match the server settings. Use the same PHP version and check memory limits. Elementor needs enough memory for large pages.
3. Edit the configuration file. Update the database name, user, and password in wp-config.php. The WordPress guide to migrating a site lists the other settings to check.
4. Test on a temporary address. Preview the new site before you change DNS. Open the homepage, a long page, and a page with a popup.

After the move: fix what the move leaves behind

1. Replace old addresses. Page data keeps full URLs, so run a search and replace for the old domain. Search & Replace for Elementor Pro does this across pages and gives you a dry-run preview first. The free version handles one page at a time.
2. Regenerate Elementor files. Go to Elementor > Tools > Regenerate CSS & Data so styles rebuild with the new paths.
3. Resave permalinks. Open Settings > Permalinks and click Save. This refreshes rewrite rules and fixes many 404 errors.
4. Check forms, emails, and integrations. Send a test form. Reconnect any service that stores your site address.
5. Set up redirects and HTTPS. Redirect the old address to the new one and make sure every page loads over HTTPS.
6. Crawl the site. Run a crawler to find broken links and missing images, then fix anything left.

How to use this checklist on client projects

If you build sites for clients, turn the 15 steps into a template. Add the client name, the old and new domain, and the person who signs off. After each launch, add one line about anything that went wrong, so the next move is easier.

For the most common leftover, see our posts on fixing broken links after a migration and the post-migration content checklist.

Quick checks for launch day

• Test the site on mobile and desktop.
• Check the logo, footer, and header on three different pages.
• Confirm analytics and search console are connected.
• Keep the old site available for a few days in case you need to compare.

Using the Elementor migration checklist: common questions

How long should an Elementor migration take?

A small brochure site can move in an hour. A large site with many templates, popups, and forms needs half a day for the move and a day for testing. The longer part is the checking, not the copying.

Should I use a migration plugin or move things by hand?

Both work. A migration plugin is faster and has fewer typing mistakes. A manual move gives you more control. Whichever you pick, the clean-up steps in this list are the same.

Do I need to keep the old site running?

Yes, for a few days. It lets you compare pages, copy anything you missed, and roll back if a serious issue appears.

What is the most common step people skip?

Replacing the old domain inside the page data. The site loads on the new address, so people assume it is done, and the leftover links show up weeks later. Step 10 prevents that.

Can I reuse this list for client sites?

Yes. Copy it into your project tool, add the client and domain names at the top, and add notes after each launch. A list that improves with every project is worth more than any single tool.

Conclusion

A solid Elementor migration checklist turns a stressful move into a repeatable routine. Back up, copy carefully, then fix the addresses and styles that the move leaves behind.

If you want to speed up step 10, start with the free plugin and upgrade when you manage many pages.