How to prepare an online store for migration to Shopify
Prepare product data, catalogue structure, delivery, payments and old URLs for a Shopify migration. Define the scope and checks before switching stores.
Practical lessons from migrating BMWParts.bg to Shopify: a courier integration, a catalogue with 114 BMW generations, payments and data checks.
I migrated BMWParts.bg from CloudCart to Shopify. The scope covered 180 products and 408 prepared old-to-new URL mappings. These are scope figures, not a measurement of traffic, rankings or sales.
The project used the courier app for collection-point selection. The implementation needed adjustments to its presentation and behaviour on mobile.
I adjusted its appearance with custom CSS. This was an observation from the BMWParts.bg integration, rather than a rating of the app across all stores.
If you are choosing a delivery app, do not stop at "does it work". Run a test order, go through the whole office selection on a phone, and only then decide whether you want someone else's code on your checkout.
Check Shopify Payments availability and the requirements for the business, its verification and bank account in the official Shopify documentation. Availability in a country does not establish that an individual store has been approved.
Payout timing depends on the account, its payout schedule and bank processing. Check the current terms before planning cash flow.
In the previous version of BMWParts.bg, navigation was organised as a list of BMW series. During the migration I chose a two-step menu: first the series, then the generation. This was a project decision based on the catalogue and how customers search for parts, rather than a limitation attributed to the previous platform.
Enlarge The result is 114 generations in 10 model families. The collections are automatic. Products carry tags like bmw-model-e60, and each generation is a collection with the rule "tag contains bmw-model-e60". Once a product gets the tag, it joins the collection by itself.
The product page also has a "BMW models" block listing the models the part fits. Each one links to that generation's collection, so one click shows only parts for that model. That was quite custom work, and I really liked how it turned out.
Enlarge I do not add compatibility on a guess. When the source data does not support a product-to-generation link, I leave it unassigned. The buyer still needs to check the VIN and equipment before ordering.
None of this is a promise of rankings or traffic. I do it before changing the platform, not after.
Official documentation: