# Moving a custom platform to Shopify, without losing what it does.

> We move brands from in-house and bespoke commerce platforms to Shopify. A fixed-fee Migration Blueprint comes first: we read the code and the database, specify the data exports, and map each business rule and integration to Shopify. Then a phased build moves what earns its place and retires the rest.

Migrations to Shopify · Custom platform to Shopify

- **Starts with:** A fixed-fee Migration Blueprint
- **Typical build:** Phased, each phase priced before it starts
- **You own:** The code, the export scripts and the documentation

## When should a custom platform move to Shopify?
- The platform depends on a few developers, and some have already left.
- Features Shopify includes, like discounts or gift cards, are built and maintained in-house.
- Security, payments compliance and hosting take engineering time away from the roadmap.
- Integrations are point to point, and changing one means testing all of them.
- Nobody can say with confidence which custom features customers still use.

## How does a custom platform migration run?
1. **Audit the code and data** — Code, database schema, integrations and a rankings baseline, read at the source.
2. **Map rules and data** — Each rule to a Function, an app or nothing; every table and URL mapped.
3. **Build exports and storefront** — Export scripts written for your schema, a theme or headless storefront built.
4. **Rehearse the move** — Repeatable loads, reconciled counts, redirects tested, integrations run against real data.
5. **Cut over and watch** — A staged switch timed to your trading calendar, rollback ready, then hypercare.

## What your platform does, mapped to Shopify
- A feature inventory: move, rebuild or retire each one
- Business rules mapped to Shopify Functions or custom apps
- Export specifications for products, customers and orders
- Integration contracts against Shopify’s APIs and webhooks
- Every URL mapped, with a tested redirect plan
- A theme or headless recommendation, with the reasons
- A customer activation plan, since passwords cannot move

## What usually goes wrong
- **Rebuilding every custom feature on Shopify** — Some are standard on Shopify; some nobody uses any more.
- **Exporting data without cleaning it first** — Find duplicates and orphaned records in rehearsal, not at launch.
- **Documenting integrations from memory** — Read the code; write each contract down before rebuilding.
- **Guessing at the URL patterns** — Crawl the live site; custom routes hide in odd places.

## Questions
### How do you get data out of a platform with no export?

We write the exports. After reading your schema, we build scripts that pull products, customers and orders into Shopify’s format and clean them on the way. They run the same way every time, so each rehearsal loads identically and the counts reconcile.

### What happens to the business rules built into our platform?

Each one is listed and given a home. Cart and checkout rules usually become Shopify Functions. Larger workflows become custom apps. Some turn out to be standard Shopify features, and some are no longer needed. The Blueprint records the decision for each.

### Can our existing integrations keep working?

The systems can stay; the connections are rebuilt. Your ERP, warehouse or CRM talks to Shopify through its APIs and webhooks instead of your old platform. The Blueprint writes each contract down: what moves, how often, and which system owns the record.

### Should we go headless to keep the flexibility we had?

Only if a theme cannot carry what your storefront does. Much of the flexibility you built can live in Functions and apps behind a theme. Where headless is right, it is Hydrogen on Oxygen, or Next.js with Shopify’s Hydrogen library on Vercel when the storefront is one surface among several.

### What happens to customer accounts and order history?

Shopify cannot import customer passwords from most platforms, so customers are invited to activate their accounts, and we plan that message with you. Order history can be imported from your exports, so customers and your service team still see past orders.

[Request a Migration Blueprint](https://www.studioantipodes.com/start-a-project)