- What’s the Difference Between a Deployment and a Migration?
- How Migrations Work
- What Happens After Finalizing the Migration?
- Troubleshooting Common Migration Issues
- Summary of Migrating Your Site
- Conclusion
Migrating a WordPress site can feel overwhelming, but with StellarSites Migrations, it doesn’t have to be. This guide walks through a migration, how it works inside the Solid platform, and the steps involved in successfully moving a site from one host to another. By the end of this document, you’ll know how to confidently migrate a WordPress site to StellarSites (or any supported destination) using StellarSites Migrations.
What’s the Difference Between a Deployment and a Migration? #
In the Solid platform, the terms Deployment and Migration refer to two different processes:
- A Deployment is about publishing or promoting code or content from one environment (like staging) to another (like production).
- A Migration is about moving an entire WordPress site—including its files, database, plugins, themes, and media—from one host to another.
If you want to push a site live or sync content between environments, see Solid Deployments 101. If you’re moving a whole site from one server to another, you’re in the right place.
⚠️ Important Notes
To use migrations, your origin site must be on a working domain with DNS properly configured. Temporary or placeholder domains (e.g. sitename.tempurl.com) are not supported for migrations, as migrations is intended to be used when migrating your existing website to another server.
There are several post-migration steps that we take to ensure that your site works smoothly on StellarSites. We strongly advise customers to migrate site using our built-in tool, rather than using 3rd party tools, to avoid any disruption.
How Migrations Work #
StellarSites Migrations automates most of the work in moving a WordPress site to a new location, but some steps still require user action, especially around DNS changes and final verification. Below is a breakdown of each step involved in the process.
Connecting to the Origin Site #
To begin the migration process, you’ll need access credentials for your original WordPress site. These are required so StellarSites can test the connection, add the origin site to Solid Central, and begin the automated migration process.
Make sure you have the following:
- SFTP or SSH credentials for the server where your origin site is hosted
- WordPress Admin login for the origin site
- Path to the WordPress installation on the origin site.
What is the WordPress Path?
Solid Migrations (the engine powering StellarSites Migrations) connects to your site using SSH or SFTP, essentially “alongside” WordPress, allowing it to have access to your site that WordPress itself can’t grant it. So once connected to your server, it needs to be pointed in the direction of the wp-config.php file (among other things) in order to migrate the site. If you’re having trouble finding the WordPress path (where WordPress itself is installed) the easiest way is to “ask” WordPress itself where it thinks it’s installed, by going to your WP admin > Tools > Site Health > Info > Directories and look for “WordPress directory location.”
Once entered, StellarSites will verify the connection automatically and begin preparing the site for migration.
Transfer Files & Database to Destination #
All site files and the full WordPress database are copied to the destination environment.
This will overwrite any existing site at the destination. Be sure to back up the destination site beforehand if needed.
The time required to complete the deployment varies, but is typically around 10-15 minutes, depending on site size. Very large sites will take longer.
You do not have to be present for the migration to progress. The migration card in the timeline will always reflect the current status of your migration, and you can click on “Read Logs” to get more details.


Initial Search & Replace on Destination #
Once the content is in place, StellarSites Migrations runs an automated search and replace on the database to adjust URLs, file paths, and environment-specific values, so that it reflects the destination, rather than origin site. The URL from the origin site is replaced the temporary URL of your StellarSite.
Preview Migrated Site at Temporary URL #
After the migration completes, you’ll receive a temporary preview URL to inspect your site before updating your DNS.
This temporary domain is typically a randomly generated subdomain, such as:
doubleholiday.stellarwp.site
🔍 Note: The subdomain (e.g., doubleholiday) is just an example — yours will be different and randomly generated for your site.
This URL allows you to:
- Preview the full migrated site in a live environment.
- Test navigation, media, forms, and critical functionality.
- Access the WordPress Admin to verify settings and content.
⚠️ This temporary domain is not meant for live traffic. Some plugins or code may behave differently until your real domain is pointed to StellarSites.
It is important that you use this opportunity to validate your site before going finalizing the migration and going live with the new site.
Migrate Again or Cancel (Optional) #
If you need to apply updates to the origin site after previewing the migrated site, you can re-run the migration to overwrite the destination with the latest version.
At this stage, you also have the option to cancel the migration if you decide not to proceed.
Continue and Finalize Migration #
When finalizing the migration, StellarSites Migrations runs one final search and replace on the destination site to ensure no lingering references to the old domain or file paths remain.
Update Your DNS Records #
When you’re satisfied with the preview, it’s time to make the migration live by updating your DNS records to point to the new destination host. These updates can be made automatically using Entri, or manually if needed.
Automatic DNS Updates with Entri #
Entri is a service that allows you to update your DNS records automatically. You authorize Entri to access your DNS provider, then follow a few quick steps to make the changes. This method delivers a smoother and more streamlined migration experience.
Manual DNS Updates #
If you prefer, you can update your DNS records manually. This typically involves logging into your DNS provider (such as Cloudflare or GoDaddy) and updating your CNAME record to point to the new host’s IP address or URL, or changing your nameservers. The migration tool will advise which course of action you need to take to update your DNS.
Connecting Your Custom Domain to Your StellarSites Website for more information.
Note: DNS changes may take up to 24 hours to propagate, though many update within a few minutes.

Final Cleanup #
These final housekeeping tasks ensure your Solid Central dashboard reflects the correct site status.
Additionally, once the cleanup is complete, StellarSites is notified to update the site’s domain information accordingly.
- The origin site is disconnected from Solid Central.
- Backups (NextGen) from the origin host are stopped. All future backups will come from the destination.
- Timeline entries associated with the destination are removed.
- The origin site’s historical timeline and migration records are preserved.
- Central now treats the destination site as the “official” site.
Final Manual Verification #
Now’s your chance to walk through your site as a visitor would. Test the front end and admin area, check for broken links and missing assets, and confirm login functionality.
A successful verification means the site is now live and running from the destination host.
What Happens After Finalizing the Migration? #
Once finalized:
- You’ll manage the destination site in Solid Central going forward.
- Scheduled backups will now come from Solid Backups — NextGen.
- All historical logs and timeline entries for the origin site are kept, but the connection has been removed.
This ensures your history stays intact while shifting control and responsibility to the new host entirely.
Troubleshooting Common Migration Issues #
If the migrated site doesn’t look right during preview or after DNS propagation, here’s what to check:
- Check that all files and database content were copied correctly.
- Look in the destination server’s PHP error logs or the WordPress debug log.
- Consider rerunning the migration (Step 4).
- Double-check DNS propagation status with tools like whatsmydns.net.
Summary of Migrating Your Site #
Here’s how to put it all together:
- Choose the site you want to migrate from your Solid Central dashboard.
- Select “Migrate site” and follow the prompts to choose the destination host.
- Wait for the files and database to transfer.
- Preview the site at the temporary URL.
- If satisfied, update your domain’s DNS settings to point to the new destination.
- Allow time for DNS changes to propagate.
- Return to Solid Central and finalize the migration.
- Confirm that everything works as expected.
- Let Solid perform a final cleanup to close out the process.
Conclusion #
StellarSites Migrations gives you a fast, repeatable, and low-risk way to move sites between hosts or into StellarSites. The process is built for confidence, from automated transfers and smart search-replace to DNS guidance and Central integration.
Want to automate even more? Subscribe for updates and early access to zero-downtime deployments, rollback options, and advanced multi-environment workflows.