Troubleshooting
Elementor Not Working After Migration: Causes and How to Fix It

Short answer
Elementor usually breaks after a migration because its data still uses the old URL, its CSS files are stale, or the new server is set up differently. Use the Replace URL tab in Elementor Tools, click Regenerate Files and Data, clear all caches, then resave permalinks and reconnect Elementor Pro.
Key takeaways
- Use Elementor's Replace URL tool after changing domains.
- Regenerate Files & Data rebuilds stale CSS.
- Run a serialized-safe search and replace if needed.
- Mixed content can stop the editor from loading.
- Reconnect the Pro license on the new domain.
- Resave permalinks to fix 404 errors.
Why is Elementor not working after migration?
Elementor usually breaks after a migration because its stored data still points to the old URL, its generated CSS files are stale, or the new server has different settings, permissions or caching.
Common symptoms are pages that look unstyled, images that do not load, an editor that spins forever, or a Pro license that suddenly shows as inactive.
The site's content is almost always intact. Elementor saves layouts in the database, and the problem is how those layouts are being displayed on the new host or domain.
Work through the fixes below in order. Most sites are back to normal after the first three steps. Take a backup of the new site before you start.
What are the common symptoms and their causes?
Each symptom points to a likely cause, so match what you see to the table before you start changing settings.
| Symptom | Most likely cause |
|---|---|
| Pages look unstyled or half-styled | Stale Elementor CSS files or old URLs in CSS |
| Images and backgrounds missing | Old domain still stored in Elementor data |
| Editor loads forever | Mixed content, cache, or blocked scripts |
| Mixed content warnings | Old http URLs on an https site |
| Pro widgets missing or license inactive | License tied to the old domain |
| 404 errors on pages | Permalinks not refreshed on the new server |
| White screen or critical error | PHP version or memory limit differences |
Elementor's own help page on site migration issues lists the same core fixes, so you can cross-check as you go.
How do you replace old URLs in Elementor?
Go to Elementor > Tools, open the Replace URL tab, enter the old and new addresses, and run the replacement, after first updating the WordPress and Site Address in Settings > General.
Elementor stores layouts as JSON data that a basic search and replace can miss. Its Replace URL tool updates those records in a way Elementor understands.
Enter full addresses including the protocol, such as https://oldsite.com and https://newsite.com. Do not add a trailing slash unless both have one.
Elementor explains this on its page about a URL change that disrupts Elementor. The Tools menu location can vary a little between versions, so look in the Elementor admin menu if you do not see it.
Should you also run a full database search and replace?
Yes, if the migration plugin did not replace URLs everywhere, run a full search and replace that handles serialized data so other plugins, widgets and options also use the new domain.
Tools such as Better Search Replace or the WP-CLI search-replace command are built for this. Both handle serialized data safely.
Always run a dry run first and take a database backup. A wrong replacement, such as a partial domain, can damage data across the site.
Our guide on how to search and replace in the WordPress database covers the full process step by step.
How do you regenerate Elementor's CSS files?
Go to Elementor > Tools, stay on the General tab, and click Regenerate Files & Data, then clear every cache on the site.
Elementor writes a CSS file for each page and stores it in the uploads folder. After a move, those files may contain old URLs or may not have copied over at all.
Regenerating deletes the old files. Elementor rebuilds them on the next page load with the current settings and addresses.
Older versions label the button Regenerate CSS. It does the same job. Afterwards, follow our guide on how to clear cache in WordPress with Elementor so no layer serves the old files.
How do you fix mixed content after a move to HTTPS?
Replace every http version of your domain with https in the database, check your WordPress and Site Address settings, and clear caches so the browser stops loading insecure files.
Mixed content happens when an https page loads images, fonts or scripts over http. Browsers block some of those requests, which can stop the Elementor editor loading.
Open the browser console to see which files are blocked. The Chrome DevTools console guide shows how to read the warnings.
Use Elementor's Replace URL tool for the http to https swap, then a full database replace. Our guide to fixing mixed content warnings covers stubborn cases.
How do you reconnect your Elementor Pro license?
Go to the Elementor license page in your dashboard, disconnect the old connection, then connect again with your Elementor account so the license is tied to the new domain.
Elementor Pro licenses are activated per site. After a domain change, the license may still be registered to the old address, so Pro widgets and the Theme Builder can stop working.
In your Elementor account, check that the license has a free activation slot. Remove the old site from the list if it is no longer live.
If you moved to a staging domain first, remember to reconnect again when the site moves to its final domain.
Why do Elementor pages show 404 errors after migration?
Pages return 404 errors when the new server has not rebuilt its rewrite rules, so resave your permalinks and check that the server supports them.
Go to Settings > Permalinks and click Save Changes without changing anything. That refreshes WordPress's rewrite rules.
On Apache servers, also confirm the .htaccess file exists and contains the standard WordPress rules. Our guide on how to flush permalinks explains both checks.
On Nginx, the host must configure rewrite rules in the server block. Ask your host if 404s continue after resaving permalinks.
Could the new server's settings break Elementor?
Yes, a different PHP version, a lower memory limit, missing PHP extensions or strict security rules on the new host can stop Elementor loading or saving.
Check Elementor > System Info and Tools > Site Health on the new site. Compare PHP version and memory with what Elementor recommends.
Raise the memory limit if it is low. Our guide on how to increase the PHP memory limit covers the usual methods.
Server firewalls such as ModSecurity can block Elementor's save requests. If saving fails with a 403 error, ask your host to check their firewall log.
What if the uploads folder did not copy correctly?
If the elementor folder inside wp-content/uploads is missing or not writable, Elementor cannot store its CSS files, so pages load without styles.
Check that wp-content/uploads exists on the new server and that WordPress can write to it. Folder permissions of 755 and file permissions of 644 are typical.
Some migration tools skip large folders or time out partway. Compare file counts between the old and new uploads folders to make sure nothing is missing.
Once permissions are right, run Regenerate Files & Data again so Elementor rebuilds its files in the correct place.
How do you test for plugin conflicts on the new host?
Disable caching, optimisation and security plugins first, then test Elementor, because these are the plugins most often affected by a change of server.
Optimisation plugins may have cached minified files that point to the old domain. Clear their cache or turn off minification while you test.
Security plugins sometimes lock rules to the old server's IP address or paths. Reset or reconfigure them after the move.
If the editor still fails, follow our guide on Elementor editor not loading for a full conflict test.
How can you avoid Elementor problems in future migrations?
Use a migration tool that handles serialized data, update URLs before regenerating CSS, and always finish with Elementor's Replace URL, Regenerate Files & Data and a full cache purge.
Keep a short checklist for every move: back up, migrate, update site URLs, run search and replace, use Elementor's tools, resave permalinks, reconnect Pro, clear caches and test.
Test on a temporary URL or staging copy first when possible. That gives you time to fix problems before visitors see them.
Finally, check a sample of pages, templates, popups and forms. Theme Builder templates and popups are easy to forget, and they often hide old URLs.
Frequently asked questions
Will migrating my site delete Elementor designs?
No, as long as the database moved correctly. Elementor stores layouts in the database, so they travel with it. Missing styles after a move almost always come from old URLs or stale CSS files, which the Replace URL and Regenerate tools fix.
Do I need to reinstall Elementor after migration?
Usually not. Reinstalling rarely fixes migration problems, because the issue is in stored URLs, generated files or server settings. Try Replace URL, Regenerate Files and Data, cache clearing and permalink resaving first, and only reinstall if files are clearly corrupted.
Why does Elementor Pro say my license is not active after moving?
Pro licenses are tied to the site address. After a domain change, disconnect and reconnect the license from the Elementor license page, and remove the old site from your Elementor account if you have used all activations.
Why are only some images missing after migration?
Images set in Elementor backgrounds and some widgets store full URLs in Elementor data. A standard search and replace may miss them. Run Elementor's Replace URL tool, then regenerate files, and check that the uploads folder copied completely.
Should I use a migration plugin for Elementor sites?
Yes, a reputable migration plugin is the easiest route because it moves files and the database together and replaces URLs safely. After any migration, still run Elementor's own tools and clear caches to finish the job.
Sources
- Site migration issues Elementor Help Center
- WordPress URL change disrupts Elementor functioning Elementor Help Center
- wp search-replace WordPress Developer Resources
- Better Search Replace WordPress.org Plugins
- Console overview Chrome for Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


