A Shopify Premier Agency for your migration
ZAGO is a Shopify Premier Agency based in Malmö and Stockholm. We connect the migration work to the decisions around it: what your next store needs, how your team will manage it, and what must be ready before launch.
What a migration project can include
We review your current platform, catalogue, content, search traffic and day-to-day workflows. Together we decide what to keep, improve or retire. You receive a proposed scope, dependencies, estimate and delivery plan before the build starts.
We map products, variants, images, collections, customer records and content to Shopify. We agree which historical orders and custom fields are needed, test a sample import, then reconcile the agreed records. Marketing consent is carried over from the source data; it is never inferred.
We agree the design direction before development. The build uses Shopify sections for the pages your team edits, with custom functionality scoped where the business needs it. Product discovery, mobile layouts and the route to checkout are reviewed together.
Payments, delivery rules, ERP or PIM connections, reviews, email and subscriptions each need their own check. We confirm what can transfer, what needs rebuilding and which providers must take part. Subscription billing dates and supported payment methods are planned separately from the product import.
The launch scope covers agreed URL redirects, metadata, analytics, test purchases and an operational checklist. We plan the final data sync and domain switch with named owners. Your team receives a walkthrough, working instructions and a prioritised list of any remaining improvements.
Know what is moving before anything moves
A product export is only part of the job. A migration also changes how stock reaches the store, how customers find products, how subscriptions renew and how your team publishes content.
We turn those dependencies into a practical plan, with review points before the decisions that are expensive to undo.
From the first review to launch
We inspect the source store and agree the destination structure. The output is a data map, integration list, page list and launch dependencies. You approve the scope and budget before design and development.
We work in a separate Shopify environment while the current store stays in use. You review the main page designs and a representative data sample. We resolve mapping and functionality issues before the full import.
We check mobile journeys, test orders, shipping, taxes, customer emails, integrations and redirects. Together we agree the final sync, any content freeze, the launch window and what would trigger a rollback. The launch decision follows the checklist.
After the switch, we check the live store, key URLs and tracking against the agreed baseline. We document the setup and train the people using it. The length of post-launch support and any ongoing improvement work are agreed in the project scope.
Gardinex: from headless to native Shopify
Home textiles · Sweden
Gardinex wanted a store the team could manage more easily. ZAGO moved the storefront from a headless setup to the Baseline Shopify theme.
The work included colour filtering, size guides and a custom sizing quiz, keeping the product-selection tools the business needed within a more manageable storefront.
Gardinex: the storefront we delivered
A native Shopify storefront
The delivered homepage pairs Gardinex’s interior photography with direct routes into the curtain range.
Product selection in context
A detail from the Gardinex project. Brand presentation and practical product guidance were part of the same build.
HappyHay: WooCommerce to Shopify
Pet care · United Kingdom
For HappyHay, the move involved both a new storefront and an active subscription business. ZAGO rebuilt the agreed pages in Shopify and handled the WooCommerce data migration.
Recharge subscriptions were migrated in stages around billing dates. The delivery also covered the hay calculator, navigation, reviews and loyalty integrations. The practical lesson: recurring orders need a migration plan of their own.
HappyHay: discovery and product pages
Browse by animal and product
The collection view organises the range around the pets customers shop for.
A clearer product page
Product photography, purchase options and feeding information sit together in the delivered Shopify design. Project screenshots are shown as delivered.
Plan for the traffic you already have
Before changing URLs, we review search queries, landing pages and the pages that bring enquiries or sales. That gives the redirect plan a clear priority order.
- Map important old URLs to the closest relevant new page.
- Review page titles, descriptions, canonical URLs and language versions.
- Check internal links and structured data against the visible content.
- Verify the sitemap, indexability and key redirects after launch.
- Compare search and conversion data with the pre-launch baseline.
Rankings can change during a platform move. We plan and monitor the transition; we do not promise a migration with no fluctuations.
Questions before moving to Shopify
Yes. We start by checking catalogue structure, custom functionality, content and integrations. WooCommerce plugins and Magento extensions do not transfer as working Shopify features: we assess what needs a native feature, an app or custom development. We also work with Wix migrations and headless-to-native Shopify moves.
The estimate depends on the data, page designs, integrations and launch requirements. An active subscription business or several markets usually requires a different plan from a small catalogue. Send us your store URL, platform and main requirements, and we can define the assessment needed for a reliable quote.
We set the schedule after reviewing scope and access. Data cleanup, design approvals and third-party integrations can all affect it. The delivery plan identifies those dependencies and the decisions needed from your team before a launch date is agreed.
Customer profiles can be imported, but passwords from another platform cannot be carried over through Shopify’s customer CSV import. We plan the appropriate account activation or sign-in experience for the chosen Shopify account setup and agree any customer communication before launch.
We check the current subscription app, payment provider and supported migration route before committing to a transfer. Billing dates, pending renewals and customer actions must be accounted for. Some payment methods may require customers to enter their details again. HappyHay’s staged Recharge migration is an example of why this needs separate planning.
The new storefront is normally built separately while the current store remains available. The final sync and domain change need a coordinated launch window. We agree any restrictions on orders or content changes in advance, based on the systems involved.
Not every migration needs Plus. We assess the plan against your operational needs, international setup, B2B requirements and required platform capabilities. Plan and app costs are reviewed alongside the implementation scope.
Let’s look at your current store
Share your store URL and what is prompting the move. Tell us about any subscriptions, integrations or markets that need particular attention.
We will review the starting point and suggest the next step towards a scoped migration plan.