An established skincare retailer was preparing to migrate its B2C storefront from Magento to Shopify.

The project involved more than rebuilding the existing website on a different platform. It created an opportunity to reconsider how product information, reusable content and storefront components should be structured within Shopify.

The new setup needed to deliver a premium customer experience while remaining practical for the ecommerce team managing products, content and campaigns after launch.

The existing Magento structure could not simply be copied into Shopify.

Product information originated in an external product information management system, while Shopify needed to support additional content and relationships that did not fit into its standard product fields.

This raised several architectural questions: which system should own each type of information? How should external product attributes be mapped into Shopify? Which information belonged in product metafields, and which content should be modelled as reusable metaobjects? How could the custom theme consume this data predictably, and how could the setup remain understandable for the ecommerce team?

I worked closely with the ecommerce manager to translate operational requirements, product structures and content workflows into a practical Shopify architecture.

My responsibilities included advising on the structure of the new Shopify storefront, exploring requirements and workflows with the ecommerce manager, and helping define responsibilities between Shopify and the external product-data system.

I supported the mapping and migration of product information, designed the Shopify metafield structure, and modelled reusable content and relationships with metaobjects.

I also developed the custom Shopify theme, connected the storefront components to the new content model, and kept the implementation manageable for the internal ecommerce team.

My role connected technical development with the way the store would actually be operated after launch.

One of the most important parts of the migration was deciding where different types of information should be managed.

The external product-data system remained responsible for structured product information that needed to be synchronised consistently. Shopify became responsible for the commerce-specific content, relationships and presentation required by the storefront.

This separation reduced ambiguity and helped prevent the same information from being maintained manually in multiple places.

The mapping went beyond standard Shopify fields such as product titles, descriptions and images. Additional product attributes had to be translated into a structure that the custom theme could access and render consistently.

Metafields were used to store structured information associated with individual products. Metaobjects were used for reusable content models and relationships shared across the storefront.

This provided a cleaner alternative to hardcoded theme content or large unstructured text fields.

The resulting content model gave the custom theme reliable data while providing the ecommerce team with a more understandable editing experience.

It also created a stronger foundation for future development. New storefront features could build on existing structured data rather than introducing another isolated content solution.

Close collaboration with the ecommerce manager was essential throughout the project.

Many decisions during a platform migration sit between technology and operations. A technically elegant model is not successful if the internal team cannot maintain it. Likewise, a convenient editing workflow can create technical problems if the data lacks structure or consistency.

Regular alignment helped ensure that decisions around product data, content modelling and theme functionality reflected real operational requirements instead of technical assumptions.

Instead of reproducing the Magento setup inside Shopify, the storefront and its underlying structure were reconsidered around Shopify's native capabilities.

The result was a cleaner, more maintainable platform foundation for managing product content and developing future storefront functionality.