Magento 2 Redesign & Migration
Redesign your Magento store or migrate from PrestaShop, WooCommerce or Magento 1 to Magento 2: WiMakeIT scopes your data, integrations and SEO.
Your starting point
Redesign your Magento site or switch platforms?
Two different projects that often go together. Your starting point determines what can be kept and what has to be rebuilt.
Your store already runs on Magento
Your platform is still the right one, but the experience has aged: dated design, clumsy mobile journeys, weak search results, features bolted on over the years. A redesign modernises the front-end, the customer journeys and the features, based on what the audit of the existing site reveals.
You want to migrate to Magento 2
Your store runs on PrestaShop, WooCommerce or Magento 1 and is reaching its limits: catalogue, B2B rules, integrations, maintenance. Migrating to Magento 2 replaces the technical foundation: the useful data is carried over and the features are rebuilt on the new platform. For Magento 1, it is also a security issue: Adobe ended support on 30 June 2020.
Redesign or migration: the difference
A redesign evolves the existing site: its interface, its journeys or its features. A migration changes its platform or technical foundation. The two can be combined in a single project; their scope needs to be defined before the work is estimated.
The warning signs
When is a redesign or migration worth considering?
Your B2B rules are handled manually
Customer-specific prices, payment terms, restricted catalogues, reorders: the current platform can't keep up and your team compensates by hand.
Your integrations are fragile
Stock, prices or orders falling out of sync with the ERP, manual exports, connectors nobody dares to touch anymore.
Buying on mobile is a struggle
Slow pages, a checkout poorly suited to mobile. Google assesses the experience with its Core Web Vitals: main content displayed within 2.5 s (LCP), response to clicks within 200 ms (INP).
Your catalogue is hard to navigate
Technical references, compatibilities, variants: your customers can't find the right product and your customer service keeps answering the same questions.
Every change is expensive
Stacked modules, an outdated version, hard-to-maintain code: every new feature becomes a project whose cost is hard to predict.
And sometimes, there's no need to start over
A specific problem may call for a targeted optimisation rather than a full redesign or migration. Scoping is also there to tell you so.
The scope
What is carried over, what is adapted and what is rebuilt
A migration is more than ‘moving everything across’. Each element is inventoried, checked and handled according to its quality and actual usefulness.
| Element | What we check with you |
|---|---|
| Products, categories, media | Data quality, variants, technical attributes, category tree, images. Mapping checks after import. |
| Customers, orders, history | Scope to carry over and checks. Passwords, consents, reviews, loyalty schemes, subscriptions and stored payment methods are assessed case by case, depending on the source platform. |
| Features, modules, theme | What is kept, replaced by a Magento 2 extension or custom-built. Modules and themes from another platform cannot be transferred as they are. |
| ERP, PIM, CRM, payments | List of data flows (stock, prices, customers, orders, invoices), direction and frequency of exchanges, responsibilities of each tool. We connect Mercator, Odoo, SAP and Microsoft Dynamics, among others. |
| Content, URLs, visibility | Inventory of the pages that matter, mapping between old and new URLs, content to keep, improve or drop. |
The outcome of this analysis is a migration matrix validated with you before development starts.
Continuity
How do you protect your sales and SEO during the switch?
A switchover needs preparation. The goal: organise the go-live and limit the risks to your sales and visibility.
Organising the switchover
- ✓Development on a staging environment: your current store keeps selling.
- ✓Testing of orders, payments, emails and data flows with your tools.
- ✓Final data import just before go-live, followed by checks.
- ✓Switchover date chosen with you, outside your peak periods.
Limiting the risks to your search rankings
- ✓Mapping plan between old and new URLs.
- ✓Permanent (301) redirects to genuinely equivalent pages, kept for at least a year as Google recommends.
- ✓Carry-over of useful content and metadata, indexability checks.
- ✓Post-launch monitoring to quickly fix any errors detected.
Ranking fluctuations remain possible while Google crawls the new site. A rigorous method limits them; nobody can honestly promise zero variation.
Method
The stages of your project with WiMakeIT
Each stage has a goal, a concrete deliverable and your sign-off before we move on.
Scoping
Audit of the current store, your data and your integrations; defining what is carried over, adapted or rebuilt. Deliverable: inventory and project scope. Your role: approve the scope.
Design and development
Journeys, mock-ups, Magento 2 configuration and development of specific features. Deliverable: accessible staging environment. Your role: approve the screens and key journeys.
Data migration and integrations
Test imports, connection of the ERP and other tools, URL mapping. Deliverable: migration matrix and discrepancy report. Your role: check a sample of products, customers and orders.
Acceptance testing and switchover
End-to-end testing, final data import, redirects, go-live. Deliverable: pre-launch checklist. Your role: give the green light for go-live.
Follow-up
Monitoring of orders, data flows and indexing after go-live, fixes, then a move to maintenance if you wish. Deliverable: post-launch review.
References
Projects close to your business
Filtre Air BMC
Problem: an ageing site that had become too slow, partly due to a catalogue of more than 20,000 categories.
What we did: migration of the front-end to Hyvä.
Result: 99% on GTmetrix (measurement published in August 2026).
Technilevage
Problem: a recent Magento 2 site that did not meet the client's expectations.
What we did: redesign of the existing Magento 2 site and migration of the front-end to Hyvä.
Result: a faster site (99% on GTmetrix, measurement published in August 2026) tailored to the client's B2B operations.
Budget
What budget and timeline should you expect?
There is no single price for a Magento redesign or migration. Cost and duration depend mainly on what your store needs to do and on the state of your data. The main factors:
Also distinguish the initial project from recurring costs: hosting, maintenance, security updates and any extension licences. Scoping gives you a reasoned estimate of budget and schedule, based on your actual scope.
FAQ
FAQ about Magento redesign and migration
Let's talk about your current store
A first conversation to understand your project and tell you whether it calls for a redesign, a migration or a targeted optimisation. To prepare, gather if possible:
Published 16 Sep 2026
Need this service for your store?
30 minutes, no strings attached, with a senior technical contact.
Keep going
Our other services
Magento2 and MageOS website maintenance
Magento 2 and MageOS maintenance: security patches, monitoring, bug fixes, backups and technical support.
Online withdrawal button mandatory on 19 June 2026 — getting your Magento ready for Directive 2023/2673
28 days from the European deadline, more than 90% of audited webshops are non-compliant. What Directive 2023/2673 act...
Magento2/MageOS website creation
B2B, B2C or hybrid stores on Magento Open Source or Adobe Commerce. From analysis to launch.