Can we keep our existing theme?

Magento 1 themes do not run on Magento 2. The migration includes a theme rebuild; we strongly recommend Hyvä over Luma at this point. If you want stock Luma we can do that, but it is a worse experience for your customers.

Will we lose customer data?

No. The Data Migration Tool covers customers, orders, addresses and product data. Custom data structures need bespoke migration scripts which we write as part of the engagement. We run two full rehearsals on staging before production cutover.

URL structure is preserved where possible. Where it changes we ship a redirect map covering every old URL. We monitor crawl errors for 30 days post-launch.

How much customer-facing downtime?

Aim for under 4 hours of read-only mode during the cutover. We schedule it in your lowest-traffic window. The full procedure is rehearsed twice on staging before production.

What happens to our extensions?

Audited at discovery. Modules with a Magento 2 release are upgraded as part of the engagement. Modules without one need either a swap to an equivalent or a custom rebuild; you decide for each.

Magento Optimization

Magento 1 to 2 Migration

Magento 1 to Magento 2 migration done right. Data migration tool plus custom logic, theme rebuild on Hyvä, full QA.

Timeline: 12 to 18 weeks
Storefront: Hyvä-first
Data: Verified migrated
Cutover: Planned + rehearsed

Overview

What it is.

Migrating from Magento 1 to Magento 2 is not a button-press despite what some agencies sell. The data migration tool covers the easy 70 percent; the remaining 30 percent is custom-module rewrites, theme rebuild, integration replacement and extensive QA. We have done this enough times to know which corners cannot be cut. Most migrations ship in 12 to 18 weeks. Stores with heavy customisation, multi-brand setups or legacy third-party integrations extend to 6 months. We share a phased delivery plan at the end of discovery so your team can sequence customer communications.

What you get

Deliverables.

Magento 2.4.x install on your target hosting
Hyvä storefront rebuild (or stock Luma if preferred)
Data Migration Tool configuration and runs
Custom-module rewrite for any non-stock business logic
Third-party integration replacement on Magento 2
Order and customer data reconciliation
SEO redirect map for changed URLs
Two cutover rehearsals on staging before production

Honest limits

What it isn't.

Magento 1 is EOL and we do not maintain it post-migration
Some Magento 1 extensions have no Magento 2 equivalent and need bespoke replacements
Heavily customised stores get a longer fixed quote after discovery

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery (Weeks 1-2)
Catalogue customisations, extensions and integrations. Map the full migration scope.
02
2. Foundation (Weeks 3-4)
Magento 2 + Hyvä installed. Data migration tool configured.
03
3. Build (Weeks 5-12)
Custom modules rewritten, theme built, integrations replaced.
04
4. Migration rehearsal (Weeks 13-15)
Full migration run on staging twice. Reconciliation reports.
05
5. Cutover + support (Weeks 16-18)
Production migration with rollback plan. Two weeks of post-launch engineering support.

Frequently asked

Questions we get from people about to book.

Can we keep our existing theme?: Magento 1 themes do not run on Magento 2. The migration includes a theme rebuild; we strongly recommend Hyvä over Luma at this point. If you want stock Luma we can do that, but it is a worse experience for your customers.
Will we lose customer data?: No. The Data Migration Tool covers customers, orders, addresses and product data. Custom data structures need bespoke migration scripts which we write as part of the engagement. We run two full rehearsals on staging before production cutover.
What about SEO?: URL structure is preserved where possible. Where it changes we ship a redirect map covering every old URL. We monitor crawl errors for 30 days post-launch.
How much customer-facing downtime?: Aim for under 4 hours of read-only mode during the cutover. We schedule it in your lowest-traffic window. The full procedure is rehearsed twice on staging before production.
What happens to our extensions?: Audited at discovery. Modules with a Magento 2 release are upgraded as part of the engagement. Modules without one need either a swap to an equivalent or a custom rebuild; you decide for each.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Magento Optimization

Magento 1 to 2 Migration

Magento 1 to Magento 2 migration done right. Data migration tool plus custom logic, theme rebuild on Hyvä, full QA.

Timeline: 12 to 18 weeks
Storefront: Hyvä-first
Data: Verified migrated
Cutover: Planned + rehearsed

Overview

What it is.

What you get

Deliverables.

Magento 2.4.x install on your target hosting
Hyvä storefront rebuild (or stock Luma if preferred)
Data Migration Tool configuration and runs
Custom-module rewrite for any non-stock business logic
Third-party integration replacement on Magento 2
Order and customer data reconciliation
SEO redirect map for changed URLs
Two cutover rehearsals on staging before production

Honest limits

What it isn't.

Magento 1 is EOL and we do not maintain it post-migration
Some Magento 1 extensions have no Magento 2 equivalent and need bespoke replacements
Heavily customised stores get a longer fixed quote after discovery

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery (Weeks 1-2)
Catalogue customisations, extensions and integrations. Map the full migration scope.
02
2. Foundation (Weeks 3-4)
Magento 2 + Hyvä installed. Data migration tool configured.
03
3. Build (Weeks 5-12)
Custom modules rewritten, theme built, integrations replaced.
04
4. Migration rehearsal (Weeks 13-15)
Full migration run on staging twice. Reconciliation reports.
05
5. Cutover + support (Weeks 16-18)
Production migration with rollback plan. Two weeks of post-launch engineering support.

Frequently asked

Questions we get from people about to book.

Can we keep our existing theme?: Magento 1 themes do not run on Magento 2. The migration includes a theme rebuild; we strongly recommend Hyvä over Luma at this point. If you want stock Luma we can do that, but it is a worse experience for your customers.
Will we lose customer data?: No. The Data Migration Tool covers customers, orders, addresses and product data. Custom data structures need bespoke migration scripts which we write as part of the engagement. We run two full rehearsals on staging before production cutover.
What about SEO?: URL structure is preserved where possible. Where it changes we ship a redirect map covering every old URL. We monitor crawl errors for 30 days post-launch.
How much customer-facing downtime?: Aim for under 4 hours of read-only mode during the cutover. We schedule it in your lowest-traffic window. The full procedure is rehearsed twice on staging before production.
What happens to our extensions?: Audited at discovery. Modules with a Magento 2 release are upgraded as part of the engagement. Modules without one need either a swap to an equivalent or a custom rebuild; you decide for each.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Magento 1 to 2 Migration

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery (Weeks 1-2)

2. Foundation (Weeks 3-4)

3. Build (Weeks 5-12)

4. Migration rehearsal (Weeks 13-15)

5. Cutover + support (Weeks 16-18)

Questions we get from people about to book.

Tell us about your project.

Magento 1 to 2 Migration

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery (Weeks 1-2)

2. Foundation (Weeks 3-4)

3. Build (Weeks 5-12)

4. Migration rehearsal (Weeks 13-15)

5. Cutover + support (Weeks 16-18)

Questions we get from people about to book.

Tell us about your project.