Search rankings survive the move
A URL inventory and redirect plan protect the pages that already earn traffic, which is the part a migration most often loses.
Move the store with products, orders and purchase routes accounted for.
We inventory the ecommerce site and plan the destination before changing platforms or hosting. Catalogue relationships, active links and operational connections receive explicit mapping and verification at cutover.
A few clients we’ve worked with
What we do
Website migration for ecommerce businesses: migration inventory, destination preparation, cutover verification.
What website migration needs to account for.
Product identifiers may be used by providers outside the website.
Historical order data may not map directly into the new platform.
A migration needs to handle new orders received during the cutover window.
What a migration actually moves.
A migration changes more than where the files live. It moves your URLs, your search history and every integration pointed at the old address.
There is a way back
A backup, verification checks and a rollback approach mean a bad launch is an inconvenience rather than an outage.
Nothing is left behind
Content, media, forms and integrations are inventoried before the move, so the gaps are found before your customers find them.
Website migration scope.
Plan migration inventory, destination preparation and cutover verification as connected parts of the engagement.
Migration inventory
Capture products, variants, assets, customers and orders within the authorised scope. Identify which records should remain in the existing system.
Destination preparation
Map fields, identifiers and URLs. Plan redirects and verify the supported treatment of customer accounts and historical orders.
Cutover verification
Rehearse the move and check representative products, cart behaviour and integrations. Document rollback and reconciliation responsibilities.
Selected website projects across our wider practice
All case studies
“What I appreciate most is that the team always communicates openly and stays honest throughout.”
“They delivered what they said they would, on time.”
“They met all our expectations by providing great strategies based on our needs.”
Website migration deliverables.
The agreed website migration scope is documented in the following work products.
- 01
Source inventory and destination field map
- 02
URL and redirect register
- 03
Cutover, verification and recovery plan
Our process
How we approach website migration.
Inventory records and dependencies
Capture catalogue relationships, URL destinations and the authorised customer and order data scope.
[ 01 ]
Rehearse destination mappings
Prepare fields, identifiers and redirects, including account and historical-order limitations.
[ 02 ]
Verify cutover reconciliation
Check products, shopping routes and new-order handling against the migration plan and recovery criteria.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Artur Tsitou
DevOps & Backend Developer
Max Tymoshyn
Founder & Architect
Petr Savenok
Full-Stack Developer
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedWebsite migration for ecommerce businesses: questions.
Can customer passwords always be migrated?
No. It depends on the platforms and supported account mechanisms; the plan may require a verified reset or invitation flow.
Can you guarantee sales will not change?
No. We reduce avoidable technical disruption through planning, testing and monitoring, but commercial outcomes cannot be guaranteed.
Discuss website migration and the requirements behind your store.