Moving a WordPress site to SiteGround: preparation and verification

Disclosure: This article contains affiliate links. I may earn a commission if you buy through them. This is a researched guide, not a claim of hands-on testing.

Moving a WordPress site to SiteGround requires more than copying files. Preserve the domain, mail routing, URL structure, and business integrations while you change hosting. Use the migration method that fits the source site, then verify before switching visitors.

If this operating setup fits your needs, check the current SiteGround offer while you compare the requirements below.

Check whether the Migrator fits

SiteGround’s WordPress Migrator guide describes a self-service copy into a destination site. It says the tool is unsuitable for WordPress.com, local-device sites, and full multisite installations. A separate manual path may be needed for those setups.

Do not discover that limitation after cancelling the source host. Inventory the source environment first and select the appropriate method. If requesting assistance, state any nonstandard applications and clarify the scope.

Prepare a source inventory

Record plugins, theme, PHP requirements, storage, database size, forms, SMTP configuration, scheduled tasks, and integrations. Save paid-license information and identify anything tied to the old hosting provider.

Export the DNS zone and note the current nameservers. Preserve MX records and sender-authentication values for outside email. Registration, DNS, hosting, and mail are separate services even when bought in one account.

Back up before starting

Create a source backup of files and database and store it independently. Export essential content and recent transaction records where appropriate. If the destination contains anything valuable, preserve that too before copying over it.

Keep the old host active through acceptance testing. A successful transfer notification does not mean every integration works or every visitor is already using the new host.

Create the destination and migration token

The documented workflow creates the destination in SiteGround’s setup wizard or Site Tools, then generates a migration token. Install the supported Migrator plugin on the source WordPress site and provide the token through that plugin’s workflow.

Treat migration tokens and administrator access as sensitive. Use only the authorized accounts and remove temporary access afterward. Do not paste private codes into public comments or support threads.

The guide instructs owners not to point the domain at the destination yet. Preview and verification come before traffic cutover.

Pause edits or arrange synchronization

A blog can often stop publishing briefly during the final copy. A store or member site continues creating important database changes. Ask how the migration handles new orders, accounts, or comments after the initial copy.

Record when the source snapshot was created. If you edit later, make sure those changes are included before launch. Otherwise a migration can succeed technically while recent business data disappears.

Preview the destination

Use the supported preview method to check homepage, archives, article pages, media, forms, and administrator access. Inspect hard-coded URLs and any integration tied to the old server.

Test the layout at desktop and narrow mobile widths. Long titles, tables, navigation, and image-free cards can behave differently after a theme or environment change. Check logged-out pages as a normal visitor would see them.

Preserve DNS and email at cutover

Follow the confirmed connection instructions for the site. If moving nameservers, replicate the entire zone. If changing only website records, preserve unrelated mail records. The SiteGround CDN has its own nameserver requirements, so consider that separately.

You do not need to transfer the domain registration simply because hosting moves. Keeping the registrar unchanged can reduce the number of moving parts. A domain transfer adds its own eligibility and timing rules.

Keep the previous host available while caches update and while you validate the new site. Do not assume every visitor switches at precisely the same moment.

Acceptance checklist

• Important old URLs open at the correct content.
• HTTPS and redirects behave as intended.
• Mail sends and receives through the intended provider.
• Forms and integrations work.
• Menus, tables, and article templates are usable on mobile.
• Analytics and search verification remain present.
• Affiliate links still use the correct destinations.
• Backups exist and recovery access is understood.

Transactional functions require their own validation. Use appropriate test modes and verify data continuity. A functioning homepage does not prove orders or memberships migrated correctly.

Finish the operating handover

Remove temporary access, update the DNS and hosting documentation, and create a fresh backup. Record billing and recovery contacts. Review old services individually before cancellation so you do not terminate a domain or mailbox you still need.

SiteGround’s backup guide warns that deleting a site removes access to backups. Apply the same caution to the source provider: save your own archive before deleting anything.

Frequently asked questions

Can the Migrator move a WordPress.com site?

The current tutorial lists WordPress.com as unsuitable for that tool. Use an appropriate alternative process.

Does hosting migration move the registrar?

No. Domain registration is a separate service.

Should I redesign during migration?

Keep the move narrow when possible. Separate redesign makes failures easier to diagnose.

Keep the success criteria clear

Move the same useful site, preserve continuity, and test its real functions. Change the public routing only after you have a working destination and a practical rollback path.

Next step

Check SiteGround through my affiliate link against the requirements above before purchasing. Compare the current checkout and renewal terms, and keep a copy of the offer you accept.

Sources and review date

Official documentation checked October 5, 2026. Features, offers, and account eligibility can change. Editorial recommendations are based on the documented scope, not independent performance benchmarks.

• WordPress Migrator tutorial
• Migration scope
• Backup service
• CDN DNS requirements

Build the business behind the tools

The tools in this guide are part of a bigger picture. At Ecommerce Paradise, I teach how to build and run a high-ticket ecommerce business. Start with a clear business model, then choose the tools that help you execute it.

If you are still figuring out the model, read my high-ticket dropshipping guide. You will understand the relationship between your store, suppliers, customers, and profit before spending money on software.

For product research, use my high-ticket niches list to explore categories and narrow down your ideas. Go deep before you go wide.

Next, work through my supplier sourcing guide so you know how to research manufacturers and approach them about becoming an authorized dealer.

My business formation checklist helps you organize the legal and financial setup. Use it to prepare your questions and confirm the requirements that apply to your business.

Get help putting the pieces together

If you want me to help you work through your next decisions, check out my private coaching. Bring your actual questions so we can focus on what is holding you up.

If you want a complete business build, take a look at the done-for-you store service. Review the scope and choose the support that fits your situation.