Migration Service Overview
Magento 2 brings some significant changes to its core, managing customer and product data, extensions and external integrations. With the looming June 2020 deadline, what does that mean for your migration?
Maintaining Customer and Product Data
Magento 2's database structure has been entirely re-written to be better optimised for your data. This means that any extensions you've installed, that quick change in the database that was done to get something fixed is likely to show up and cause problems during your migration. A manual approach is recommended, with verification and sanity checks before importing into your new store.
Magento 2 Store Design
If you have a pre-made design, we'd recommend finding an equivalent Magento 2 version to save time and cost. We have many optimised and compliant themes we can support. Bespoke or custom code? You've guessed it, that'll need to be checked, tested and imported manually too.
Magento 2 Hosting
The brand new architecture means back office functions, the customer front-end and your database can be split out to handle your business peaks. This fundamental change also means you're likely to require between 30% - 50% more server resources to maintain your existing level of performance. Don’t worry, we’ve got a solution for that too.
Magento 1 to Magento 2 Migration ToolsThe web is awash of automated website migration tools, often low-cost and done in an hour, but what do you really get.
Simple Site? It’s Worthwhile
Running a store with a few hundreds products without customisation? These tools are perfect for you. They’ll export your data in to a Magento 2 friendly format.
Customised Site? Not So Good
These automated tools work well where product or customer data hasn’t been adjusted, either manually or by an extension. Using something else other than Magento’s in-built order manager? You’re likely to require a manual export and import.
Bespoke Site? Not Recommended
The key selling point for these automated tools is they rely on a consistent structure for data. If your store has a decade’s worth of customisations, you’re likely to spend more time debugging the output than if you were to have a manual migration, which includes full testing and verification.