7 reasons to migrate to Adobe Magento 2 with scandiweb

We know what usually goes wrong and how to avoid it

We do make mistakes. Each migration we've done since 2015 had issues we did not take into account during the planning stage. But here's what we do—we log such issues in the migration tracker along with the solution and a plan on how to avoid them in future migrations.

Your migration will be performed on top of the learnings taken from 10-12 migrations per year since 2015. Now migration to Magento 2 is finally a calm, fast, and predictable process with good results!

We have been working with scandiweb on redesigning and migrating our global eCommerce platform from Magento 1 Community to Magento 2 in Adobe Commerce Cloud. We have also performed some other projects with scandiweb, and it is a pleasure to work with them!
They are available most of the 24h x day and are always trying to find the best solutions.
eCommerce Manager at Buff
Marc Muntané

End-to-end responsibility—from the platform to SEO, data layer, user journey, and marketing

We have in-house teams for SEO, data & analytics, PPC, UX, and marketing automation that participate in each migration project for the planning and execution of non-technology work.

Your platform has been an integral part of your eCommerce operations so we make sure that the platform change or upgrade respects the platform's relationships with backend processes, marketing activities, and customer journey, among others.

Data migration and integrations are done by a specialized Data & Integration team

Data migration and integrations with 3rd-party systems are vital parts of the project. We figured it was best to have a specialized team doing only this part of the project across all of the migration projects we are doing. Their focus, process automation, and test suite help us deliver migration projects faster and with reliable results.

Our IP and tools help us complete your project faster

Since 2015, we have built tools that automate and speed up the migration process while also minimizing human error in the handling of complex data sets. For example, readymage.com automates setting up development, staging, integration, pre-live, and live environments, as well as building and deploying pipelines. Instead of scheduling DevOps for multiple weeks of work, we achieve all of the above in 15 minutes and with just one click!

Another tool called Create Magento App helps in setting up a local development environment within a few hours rather than multiple days and ensures that your development environment is optimized, correct, and ready for teamwork.

MIT trained BAs and TAs apply System Engineering to handle project complexity

Successful Go-Live is a function of a correct start. We follow the System Engineering approach in project delivery to start with high-level business goals and then decompose, define, and add acceptance criteria to each of them.

To handle complexity, we look at and describe your project's digital ecosystem, data profiles and their sources, component and modular view, low-level design, requirement traceability matrix with further tasks created in Jira, and test cases in TestLodge. We validate delivery from small tasks to modules, integrations, components, and finally whole project's conformity to the initially set goals.

We successfully couple migrations with the conversion-driven redesign

Our redesigns are informed by data and conversion research to see which parts of the user journey have to be kept intact and protected from change and where we can explore opportunities for further conversion rate and average order value increase.

After the Go-Live, when your redesign is delivered, our team monitors KPIs to make sure the site is performing as expected or whether it requires adjustments to improve results.

We increase business metrics for 100% of our customers

Want to migrate and are interested in the timeline and costs?

If you have a migration that is stuck, we can help too, check these resolved issues

If you have a migration that is stuck,
we can help too. Check these resolved issues

40% of organic traffic was lost due to mishandling of technical SEO and 301 redirects

50% of the code base is custom, development team has left, no docs, but we need to figure out what is there, what is valuable for the business and migrate it

Conversion rates dropped 30% after launch due to redesign taking only creative input instead of focus group validation and conversion rate analysis backed by data

Customer wants to migrate from Magento 1 Community to Adobe Commerce version, there is no official Data Migration Tool, but we got you covered—we have all the necessary scripts and it takes just two days to migrate default data!

Campaign management is a disaster because the migrated site did not have correct conversion tracking events set up, so AdWords never knew who from the people they sent to the site really did convert

The site is very slow due to incorrectly configured Varnish, insufficient server resources, and custom-made PHP and MySQL configuration instead of following best practices

What happens when we start the migration project with you?

Migration estimate

After the initial meeting, we plan a discovery process to analyze the current state of your eCommerce operations. We describe and define the objects to be migrated such as the platform, custom features, SEO, integrations, and data layer. The necessary time and effort to migrate them are reflected in the migration estimate that is part of the agreement.

Opportunity check

Additionally, we look into opportunities to improve your eCommerce operations by conversion-driven redesign, SEO, enhanced data gathering and analytics, scalable hosting, PIM, or OMS.

Migration roadmap

Once we start working, we share the project delivery roadmap across all the streams such as graphic design, frontend development, backend development, ERP integration, default data migration and custom data migration, technical SEO, data layer & analytics.

Weekly progress reporting & demo

Every week or two, you will be invited to a demo and receive a sprint report summarizing results achieved and updating the point where we are on the overall project roadmap.

Large milestones demo

In addition to sprint demos and reports, we also plan larger milestones on the roadmap that aggregate efforts across streams into a demo build of your project.

Milestones are usually as follows

Clean Adobe Magento 2 project is set up on a Staging server with sample data

Your default data is migrated to the Staging instance and can be checked with the default theme

ERP, WMS, or similar systems are connected to your new store and default data starts to be alive with the import of real SKUs, prices, and stocks—basic orders placed can be received in the ERP system if order export is part of the order flow

The frontend team has completed your theme and it is available for review on a separate server instance with default data—after its approval, it is merged into the Staging instance, so that your basic data that is now alive and connected to ERP systems is displayed in the correct look, feel, and layout

Extensions are set up, custom modules are coded, and custom data from the previous platform is migrated

SEO team has been working in parallel and makes sure that all content, metadata, and redirects are set up correctly

Data & Analytics team makes sure that all events on the frontend are correctly tagged and sent to the data collection platform

UAT and pre-live simulation

The site undergoes end-to-end UAT and pre-live simulation after all scope is delivered and tested internally.


Data migration scripts are updated to prepare for the go-live and delta data migration to take account of the new products, customers, and orders.

The current site sets up a maintenance page, the new site is up, the cache is warmed up, and we usually manage DNS switch with the Cloudflare to enable instant transfer and show-up of the site for all users without the need to wait for ISP update propagation.

Post-go-live monitoring

Project delivery, SEO, UX, and data layer teams continue to monitor the site during the first week of the go-live and work in close contact with the customer to make sure that all backend processes are functioning correctly and business metrics are stable.


Further growth & acceleration planning
and execution

Engage the eCommerce growth team for continuous improvement of eCommerce operations and business metrics.


How much time does migration usually take?

Depending on the site complexity and additional changes bundled with migration e.g. redesign, migration may take from 2-3 months up to 4-5, but usually never exceeds
half a year.

How much does migration usually cost?

You will get an estimate within a few days after we understand your current eCommerce operations and migration goals. Usually, we are 30-50% below top estimates because we keep our hourly rates competitive hiring globally and do many complex things much faster automating them since 2015. We are also 30-50% more expensive than the cheapest option you would get because while our hourly rates can be comparable, we see and estimate a much broader scope that we need to take care of for a successful migration than a low ball estimate.

I want to migrate to Adobe Magento from another platform, can you do it?

Yes, we migrated to Adobe Magento from Hybris, Shopify, and legacy proprietary systems. Essentially, it is data on your products, customers, and orders that needs to be transferred as well as an understanding of platform features and integrations to make sure your new platform on Adobe Magento 2 will support all usual data flows and process.

Do you migrate from Magento Community to Adobe Commerce?

Yes! We recently launched Buff global site migrating it from Community to Commerce adding a new design and React storefront from ScandiPWA during migration.

Can I keep my current hosting provider?

Sure, you can. We set up Dev, and Stage on our readymage.com infrastructure, and pre-live and Live can be set up on your preferred hosting.

Will I have ownership of the project code?

Yes, absolutely. It is stated in the agreement, that there is a one-time project fee without lock-in or code rent. You will need to revise the pricing of 3rd parties though, but we can help with that.

Brands we have migrated to Magento 2 and Adobe Commerce

Why migrate to Magento 2?

Adobe Magento is strong with its ecosystem of 3rd-parties and extensions. The platform is robust and can handle dozens of integrations, but 3rd-parties such as payment gateways, shipping, search, and personalization are not supporting integrations for Magento 1 anymore.

The ecosystem was supporting both platforms Magento 1 (released in 2008) and Magento 2 (released in 2015). However, after Magento 1 reach end-of-life in 2020, the number of extensions to support convenient payments, shipping, search, order processing, marketing automation efforts, and integrations have dramatically decreased or their integration became more expensive (via API only rather than a supported plugin).

Now is a GREAT TIME to migrate—Magento 2 is very stable and mature, not to mention that it recently got amazing upgrades in PHP and MySQL to handle large databases fast. You will be surprised by enterprise features you would see there now even in the Open Source versions such as the very popular Page Builder. Also, Magento 2 supports headless and API-driven frontends with their wide GraphQL coverage and PWA/React single-page applications.