Three ways to buy a migration, what each one includes, and how Assisted grows for a store that needs more than the baseline.
A sample, one store view and one locale, inside your own Shopify store, so you can judge the result before buying anything.
The migration is yours to configure and re-run in the app, at your own pace, with as many store views and locales as you like.
Preparation, the migration itself, the checks afterwards, and someone accountable for the plan. A larger store is more hours, not a different product.
Three store views, three locales, seventeen hours of people, and the capabilities that only count once they are configured and working. Nothing here is a ceiling: more scope is more hours, estimated before it starts.
A data migration that used to cost €10,000 and weeks of agency work now runs through the Syncer app for a fraction. No custom builds. No offline weekend. No patching redirects by hand.
A migration that would cost €10,000 with an agency runs through the Syncer app for a fraction. No custom builds, no monthly retainers.
Full migration runs in as little as one week. Live Sync keeps the old store selling until the moment of cutover.
Your shop keeps selling during the migration. The cutover is a moment, not a crisis.
Every record validated end to end. Orders, customers, SEO redirects. Nothing of what you built gets lost.
Demo and Self-serve buy software, not time. Neither includes any of our hours, and that is the real difference between €299 a month and €2,500: the same migrator, run by us instead of by the merchant.
The seventeen hours cover the baseline scope. Anything larger is estimated in hours before the work begins, which is how Assisted grows rather than stopping.
Nothing here is refused, and nothing here costs more by default. What happens depends on which of two things it is.
Still migration: a fourth store view, another locale. We check whether it fits in the hours already included. If it fits, it costs nothing extra. If it does not, we estimate only the part that does not fit.
Not migration: custom development, theme work, records that have to be built rather than moved. There is nothing to fit it into, so it gets its own line and its own price.
Both are agreed before the work starts.
Each one is its own migration run and its own validation. We check whether it fits inside the fourteen hours first. Often it does, and then it costs nothing extra. Only what will not fit is estimated and added to the quote.
Third-party extensions without an API need bespoke extraction. If the extension exposes a current API, it falls back inside standard scope.
Building products, pricing or content that has to be created rather than moved is custom development, not migration.
We migrate data into a theme. We do not build or adapt the theme.
Catalogue restructures or platform changes mid-project reset validation and are quoted as new work.
Named at kick-off, because each one has stalled a migration before and none of them are ours to fix.
An integration that is created but never activated, or granted only part of its resources, looks identical to a broken migration.
Shopify downloads images from the source itself. Bot protection or firewall rules that refuse automated traffic will silently strip images from products and drop collections entirely.
Mapping questions about variants, pricing and locales need one person who can answer them inside the project-management time.
Send us the source platform, the catalogue size and the number of store views. You get the hours and the price before anything starts.
