Migrating an Existing WordPress Site to StretchWP

Overview

Already have a WordPress site elsewhere? StretchWP can bring it onto managed hosting through a managed migration performed by the Stretch team. You provide access to the source site; the team copies it onto StretchWP, pairs it, and prepares it so you can verify everything before pointing your domain over. This is the recommended path to consolidate an existing site into your StretchSuite workspace.

The migration workflow at a glance

1. You request the migration and provide source details.
2. The Stretch team provisions a destination managed site and runs the migration.
3. You verify the migrated copy on its temporary StretchWP address.
4. You cut your domain over to StretchWP, and SSL is issued automatically.
5. The old host is retired once you're satisfied.

Steps

1. Request the migration. Contact the Stretch team (or start from the Migrate action on the Sites launcher) and tell them you want to move an existing WordPress site in. Provide:
- The current site URL.
- Access to the source (admin credentials, a migration/export package, or hosting access — whatever the team asks for).
- The domain you'll ultimately use.
2. The team runs the managed migration. StretchWP provisions a destination managed site and copies your content, database, themes, plugins, and media across. The migration runs as a managed job — you'll see migration activity and its status on the destination site's Events tab.
3. Verify on the temporary address. Open the destination site's control panel and use one-click Log in to review it on its …sites.stretchmedia.ca address. Click through key pages, check forms, and confirm media and menus look right — all before any public traffic moves.
4. Attach and cut over your domain. When you're happy, follow Connecting your custom domain: attach your domain, verify ownership with the TXT record, then point your A/CNAME records at StretchWP. SSL is issued automatically once the cutover completes.
5. Confirm health, then retire the old host. Check the Health tab shows HTTP 200 and TLS valid on your domain, confirm a fresh backup on the Backups tab, and only then cancel your old hosting.

Example

A law firm runs warne-law.com on a legacy host. They ask the Stretch team to migrate it. The team provisions warne-law.sites.stretchmedia.ca, migrates the content and database, and pairs it. The firm logs in with one click, clicks through practice-area pages and the contact form on the temporary address, and confirms everything works. They then attach warne-law.com, verify the _stretchwp TXT record, point the apex A record and www CNAME at StretchWP, and watch the Domain and SSL pills turn green. After confirming HTTP 200 / TLS valid on the live domain and a clean backup, they cancel the old host.

Tips

• Verify before you cut over. The temporary StretchWP address lets you test the full site with zero risk to your live domain. Use it thoroughly.
• Lower your DNS TTL a day ahead. If your DNS provider allows it, reducing the TTL on your records before cutover makes the switch propagate faster.
• Keep the old host until you're sure. Don't cancel your previous hosting until the domain is live on StretchWP, Health is green, and you've confirmed a backup exists.
• Note anything custom. If the source site has custom code, unusual plugins, or special redirects, tell the Stretch team up front so they can carry it over.

Troubleshooting

• A migration job shows failed on the Events tab. Note the job type and error message and share them with the Stretch team — migrations run as managed jobs, so the team can diagnose from that record.
• Something looks off on the migrated copy. That's exactly what the pre-cutover verification is for. Report the specific pages or features to the team while the site is still on its temporary address, before you move your domain.
• The domain won't go live after cutover. Ownership verified but traffic not switching means the A/CNAME records aren't pointing at StretchWP yet — re-check them against Connecting your custom domain.

FAQ

Will my site go down during migration? No. The migration builds a copy on a temporary StretchWP address; your live site keeps serving on its current host until you choose to cut the domain over.

Do my plugins come across? Yes — your content, database, themes, plugins, and media are migrated. On StretchWP, the managed core suite is also present, and the team can reconcile any overlaps with you.

How long does it take? It depends on the size of the site. The team gives you a sense of timing when you request the migration; you control the final cutover, so there's no rush to move your domain until you've verified the copy.