Magento has undergone a major overhaul with version 2.x. Also, developers of third-party features, like extensions for inventory management, now direct their resources to 2.x. To keep current, retailers need to replatform to Magento 2.x (or another platform).
When Command C began the replatforming process for NMWA, we had three overarching goals:
- Provide NMWA with a fresh start on Magento 2. The data import from 1.x would be crucial in this.
- Give the NMWA team the ability to easily manage their site on the backend.
- Improve site performance and speed for an even stronger customer experience and to increase conversions.
Here’s how we did it.
Challenge: A lot of important data lived on the original NMWA site. We wanted to leverage as much data as possible to maximize ROI and the customer experience.
Solution: Command C’s data migration strategy and execution
NMWA’s Magento 1 (M1) site had a lot of crucial data to move into Magento 2 (M2). To address this, Command C developed a strategy and execution plan for flawless data import. There were products, customers, and order history to consider. Additionally, there were extensions in the old site that would be obsolete in the new one. Plus some extensions to be transferred were so dramatically different that they couldn’t share data.
We always practice migrations in a sandbox environment prior to making changes to production environments. After we set up NMWA’s sandbox, we took a first pass at mapping the old data into the new data structure. Running test imports allowed us to uncover and remove errors and be certain that our final import into the new platform was perfect.
Bonus data challenge: the NMWA site runs an embedded ERP extension. This required additional data structures on top of Magento’s core data structure. To solve for this, Command C wrote custom script for making sure that the ERP was aware of new products.
Challenge: Minimize administrative frustration
Solution: Eliminate duplication of tasks and streamline the backend
On Magento 1, the NMWA team was having to duplicate tasks. For instance, the way the CMS was structured required them to create content in multiple places. Command C wanted to decrease the number of times they would need to curate content when they added new brands or new products. So we helped NMWA select a theme with a blog module. Then we migrated their legacy Tumblr posts into this new module. Now the writers blog directly within Magento.
Additionally, the previous NMWA site had a page called Collective Action. Customers came to the page to vote on their favorite products and other things–and they loved it. People would look at new products, vote, and come back and re-engage with the site. In helping NMWA select a Magento 2 theme, we selected one with a portfolio module built into it. We saw that we could leverage the portfolio module to re-create this dynamic feature and keep engaging customers. Through these things, we helped transfer NMWA’s long-standing customer base to new site experience. We were also able to maximize ROI by leveraging a pre-existing theme.