For an American client, who is a doctor (let’s call him Dr. Mystery) by profession, we had to perform a complete migration from Magento 1 to Magento 2 Enterprise. As is the case with some of our clients, we have to honor a non-disclosure agreement so hence we will only be discussing his case study without mentioning his name/website. So, a little background about the client, his site basically sold supplements and health-related products created by Dr Mystery himself. Some of the examples of his products include: Hair Formula, Liver Cleanse etc. In a personal capacity, the client also has a health and wellness clinic in Alexandria and provides free consultancy. Pretty cool, right?

Moreover, the client reached out to us for a dedicated remote engagement to migrate his supplement store to Magento 2 Enterprise and we assigned one of our most senior Magento developers to undertake this monstrous task. This was a relatively new challenge for us, as we had performed migrations to M2 in the past but this was the first time one of our resources was performing a migration to Magento 2 Enterprise. As always, RLTSquare never backs down from a challenge and we proceeded with finalizing the scope and got to work.

 

The Magento Migration Process To M2 Enterprise

As the project began, we dissected the scope into 3 phases.

In phase 1, we basically engaged in database migration that included migrating the entire order information so that no orders are lost. Similarly, the customer information/details were migrated as well. Once all this essential data was secured, we made way into phase 2.

In phase 2, we listed down all the features and functionalities that the installed extensions were performing on both the front-end and the back-end of the client’s old Magento 1 website. So the basic method to go about this was:

  • Check if the same vendor is providing a compatible extension in Magento 2
  • Check if a different vendor is providing an extension with required functionality in Magento 2
  • Customize an extension available in Magento 2 if it is not performing all the required functions
  • Build a new module/extension to bring the required functionality in the new M2 store
  • Customize all extensions to be compatible with Magento 2 Enterprise if not already available

Some of the extensions that required customization for this client’s supplement store included:

– Partial Customization on Subscription and Recurring Payment (Available by the same vendor in M2)

– Partial Customization on TaxJar (Available by the same vendor in Magento 2)

– Created modules for some APIs that had no existing extensions

– Integration of Wicked Reports extension

– Created a module for Rakuten Affiliate Network integration

– Created a module for Skubana integration (warehouse management system)

– Multiple Order Email Extension in Magento 2: This was the extension that was available in Magento 2 community only so we had to customize it to make it compatible for client’s new Magento 2 Enterprise store. Moreover, this particular extension was only compatible for versions older than Magento 2.2 so customization was done to further make it compatible with Magento 2.2.

 

Moving on to the third phase of theme development, we started out with the LUMA theme as we believed it was the most suitable to paint the client’s imagination of his Magento 2 Enterprise store on LUMA’s canvas.