Make your site better.
Migrate by the book.
Site looking dated, platform no longer a fit, pages loading slowly? We redesign, replatform and move your data. What can be migrated, how cutover works and how we roll back if something goes wrong all go into the plan after the review, and we start only once you’ve approved it.
Drag the center handle to compare before and after · Illustration
- Assess firstWritten migration checklist
- 301Every old link redirected
- ItemizedData counts verified
- ReversibleRollback plan before cutover
Safety isn’t a promise. It’s five checkpoints.
Each checkpoint produces a written deliverable. We only move on once you’ve reviewed and approved it.
- 01
Migration feasibility review
We audit the old platform’s data structure and the new platform’s capabilities, then sort everything into three lists: migrates directly / needs rebuilding / can’t be migrated. Customer passwords, for example, usually can’t be migrated directly.
Output: migration checklist - 02
Data verification
Products, customers, orders, blog posts and categories are exported, cleaned and imported. We check the counts for each type and spot-check fields such as price, inventory and images.
Output: data check sheet - 03
URL mapping (301)
We crawl the old site’s links and map each one to its new address with a 301 redirect. After launch we monitor 404s and fix anything we missed.
Output: URL mapping sheet - 04
Cutover plan
It spells out the cutover window, admin freeze, incremental sync, domain switch and launch checklist. Cutover runs during your lowest-traffic hours, with someone on watch throughout.
Output: cutover timeline - 05
Rollback plan
Before cutover we keep the old site and its original DNS records, and agree on the criteria in advance: if key checks fail, we point the domain back to the old site as planned.
Output: rollback plan
Exactly what can be migrated, how cutover works and the timeline depend on both platforms’ data structures and the size of your store. We write them into the proposal after the review.
Every piece of luggage is on the list.
Migration isn’t copy and paste. Each type of data is exported, cleaned and imported separately, then the counts are checked item by item, with records you can review.
Sample data · Actual counts depend on your store
Know the route before you move.
Pick your old and new platforms to see what comes along as is and what needs rebuilding in its new home.
What can be migrated depends on both platforms’ data structures. We confirm it item by item during the review.
Help search engines match old pages to new ones.
The biggest worry when replatforming is losing organic traffic. Link mapping, redirects and content checks reduce the impact of migration on search traffic.
Illustrative curve. Actual results depend on site size, content changes and competition in your industry.
Every old link worth keeping
gets the right new home.
We collect every old link we can find, cross-check them against sitemaps and existing records, and set up matching redirects. After launch we keep checking for gaps and error pages.
- Old link inventory and checklist
- A 301 permanent redirect for each link
- Post-launch 404 monitoring and fixes
Sample links
Cutover on your quietest night,
so customers barely notice.
The new site is built and tested in advance while the old one keeps selling as usual. On cutover night we only run a final incremental sync and switch the domain, with someone on watch the whole time. If checks fail, we switch back to the old site under the rollback plan.
- 22:00Freeze admin changes
- 22:30Sync new orders and customers
- 01:00Point DNS to the new site
- 02:00Check orders, payments and redirects
- 06:00Go live, keep monitoring
Sample timeline · The actual window is set by your lowest-traffic hours. While DNS changes propagate, a very small number of visits may still reach the old site, which is why we freeze admin changes on the old site before cutover.
Common questions before the move.
01Can my old site keep selling during the redesign and migration?
Usually, yes: you can keep using the old site while the new one is being built. Whether any operations need to pause during the final cutover, and for how long, is set out in the cutover plan.
02Will migration affect my Google rankings?
Migration can cause search fluctuations, depending on how much the pages, content, URL structure and platform change. We plan ahead and keep checking, but we don’t promise that rankings will stay the same.
03Can customer accounts and passwords be migrated?
Customer profiles and order history can generally be migrated. For security reasons, passwords usually can’t be migrated directly, so we help send account activation or password reset emails.
04Can I just redesign without switching platforms?
Yes. For a redesign only, we design and build a new theme on your current platform. No data needs to move, and the timeline is shorter.
05How long does a migration take?
It depends on your data volume and the scope of the redesign. Switching platforms while keeping your design usually takes 2–4 weeks; a redesign plus migration usually takes 4–8 weeks. The details go into the proposal after the review.
06What do I need to prepare before migrating?
Access to your old site’s admin and server, your domain management account, and a list of what you want to keep and what you want to drop. We handle the rest of the data export and cleanup.