Inventory
We export every URL, content type, record count, DNS record and integration on the source, so the move has a list to check against.
[ Websites ]Website Migration
Move the website with a map and a way back.
Changing hosts, themes or platforms should start with an inventory. We record the source, map URL decisions and reconcile the content and data that must survive the move.
EngagementWebsite Migration
FormatProject
Timeline2-6 weeks
OwnershipYou own the files and accounts
[01]Fit and scope
Is this the right project for you?
Good fit if
- You are moving a site with valuable URLs or content
- Your store needs products and orders reconciled after migration
- You can agree on a content freeze and a rollback window
Not a fit if
- You need an unplanned live move without backups
- You cannot provide access to source data
- You want URLs removed without reviewing redirects
[02]Migration and replatforming
Move hosts or platforms with URLs, data and email accounted for.
Every migration follows the same three steps, whatever the source and destination. The URL map and the reconciliation sheet exist before anything moves.
Map and migrate
Data moves by script into a staging copy. Counts and key records are compared with the source, and mismatches are fixed before cutover.
Cut over and watch
Email and other DNS records are copied before the switch. After cutover we check 404s, forms and coverage daily for 14 days.
100%Source URLs with a recorded destination
0Redirect chains left at cutover
14Days of daily checks after cutover
1Rollback rehearsal on staging before cutover
[03]Inspectable artifact
The reconciliation sheet every migration ends with.
This sample uses illustrative figures from a WooCommerce to Shopify move. Your sheet lists your own record types, and it is yours after launch.
| Entity | Source (Woo) | Target (Shopify) | Method | Status |
|---|---|---|---|---|
| Products | 1,842 (3,610 variants) | 1,842 (3,610 variants) | SKU match + price checksum | Match |
| Customers | 28,417 | 28,417 | Matched by email, consent flags carried over | Match |
| Orders | 41,206 | 41,206 | Order number and total, to the cent | Match |
| Reviews | 6,118 | 6,118 | Product + author + date | Match |
| URLs | 3,900 legacy paths | 3,900 redirects | Crawl: 0 × 404 after launch | Match |
| Gift cards | 214 active | 214 active, balances equal | Code + balance | Match |
[04]Adjacent
Bigger, smaller or different?
Three doors next to this one.
S10
WooCommerce Development
WordPress stores with tested checkout, a short plugin list and updates run on staging first.
S15Speed Optimization
Core Web Vitals work measured in the field, not just in Lighthouse.
S19Ecommerce Development
Not sure which platform? We score your requirements and recommend one.
[05]Sample handoff
Migration reconciliation and rollback checklist
The sample reconciliation compares source and destination counts, key records and URL responses. It also records the freeze time, final sync and conditions for rolling back before the new site accepts production changes.
Sample · scope agreed before work starts
Migration reconciliation and rollback checklist
The sample reconciliation compares source and destination counts, key records and URL responses. It also records the freeze time, final sync and conditions for rolling back before the new site accepts production changes.
You keep the agreed project files and source. This sample illustrates the handoff; it is not a client result.
[06]Questions
Website Migration questions.
What can you migrate?
Sites and stores moving between WordPress, WooCommerce and Shopify, plus host moves for those platforms and for Laravel applications. We move pages, posts, media, users, products, customers, orders, redirects and DNS records, including email. Moves to or from Webflow, HubSpot CMS or BigCommerce are scoped on request.
How do you prevent missing content?
We record the source inventory before moving it and compare the result afterward. Exceptions are logged and reviewed instead of being hidden by a successful import message.
How are redirects handled?
Each changed URL gets an approved action and destination. We test response codes and check that redirects reach a valid page without unnecessary chains.
Can you migrate a store with active orders?
Yes, when the platform and access support a controlled cutover. We agree on a freeze or final-sync method and reconcile the order data before resuming normal operations.
Will there be downtime?
Visitors usually see none. The new site is built and tested on staging while the old one stays live, and the switch is a DNS or domain change. Stores need a short order freeze or a final sync, and your migration plan states that window before you approve the cutover.
Can our existing site stay live during the build?
Usually the new destination is prepared and tested separately. The plan defines when content must stop changing and which source remains authoritative until cutover.
How do you handle a failed cutover?
We use the agreed backup and rollback procedure. The decision point is written before launch so the team can restore the source without improvising under pressure.
What happens after migration?
We check redirects, forms, important journeys and the reconciled records. Ongoing hosting and care are separate choices, with ownership staying in your accounts.
[07]Next step
Tell us what is moving, from where and to where.
- 01 · TodayInstant confirmation and a booking link.
- 02 · 1 business dayA senior engineer reviews the source and replies.
- 03 · 5 business daysA written migration plan and fixed-scope proposal.