Card-on-file portability.
A vault you cannot export means every saved card dies on the day you move, and every subscription with it. The export path is agreed in writing before anything else starts.
Cut over.Keep the return path.
The storeRebuilt on infrastructure you own.Operated by us after it launches.
What moves with itThe catalog, the customers, the saved cards, the checkout.The money that lands from it moves with them.
✦ Twelve freezes handled✦ Twelve migrations completed✦ All twelve still trading✦ Our own sourcing and China freight✦ We run this stack on our own stores first
✦ Twelve freezes handled✦ Twelve migrations completed✦ All twelve still trading✦ Our own sourcing and China freight✦ We run this stack on our own stores first
03 / Where you areCurrent layer / Store
One loop. Current layer marked.Select any node to move through the operating system.
01 / How the move runsOld and new rails live together
Shift the weight.
Do not flip a switch.
The new store and the new rail are built beside what you run today. Both payment routes stay live while the volume moves across. The old one is switched off last, not first, so there is always somewhere for an order to land.
Audit. Build. Dual live. Shift. Verify.The backward line is the rollback path, not decoration.
02 / Three things that break quietlyHow it works
The parts that
break quietly.
Dual-rail cutover.
Both rails stay live while the weight moves across, and the new settlement pattern is checked against what it should be. Rollback stays available the whole way.
Descriptor continuity.
The line your customers recognise on their statement stays the same. Change it and disputes rise, whatever else went right that week.
03 / What moves and what is rebuiltTransfer / rebuild / name the gap
Move records.
Rebuild dependencies.
Your catalog and your customer records transfer wherever the source allows it. The storefront, the checkout and everything the store runs on are rebuilt. Anything locked inside a closed app is named before the move, never promised after it.
What transfers is not what gets rebuilt.Every installed app receives a replace, rebuild or drop decision.
04 / What happens to your rankingsThe addresses
The addresses
do not move.
URL structure is preserved with a full 301 map. Metafields and structured data are carried across. The descriptor stays the same, so the line customers recognise on their statement does not change either.
05 / How the engagement runsApplication to cutover
We show up
with your file open.
By the time the call happens we have read three months of your statements and underwriting is already running on your real numbers. The call is a findings review, not a pitch. Twelve migrations have run this way, and all twelve merchants are still trading.
Application
Your information, and authorization for us to read your processing statements and prepare real pricing. This is the gate. Only qualified operators reach a calendar.
You send three months of processing statements.Pre-qualification
We read the statements and work out whether a better deal exists before anyone books time. If it does not, we say so and that is the end of it.
Nothing further from you.The agreement
Signed electronically. The terms are in front of you before the call rather than after it.
An electronic signature.The call
Underwriting is already running on your numbers. Your current processing standards, what changes, the pricing difference, confirm and go.
Your questions, answered against your own figures.Approval and build
The vault export from your current processor is started first, because its timing belongs to them and not to us. The rails and the merchant account come up in 20 to 40 hours of work. The store rebuild runs alongside.
Every installed app gets a replace, rebuild or drop decision.Dual-rail
Both payment routes stay live while the weight moves across and the new settlement pattern is checked. Card portability and descriptor continuity stay in scope throughout.
The old route is not removed first.Cutover
Traffic and settlement move over once the new route is proven. A full migration runs 7 to 10 days at the outside.
The previous route stays recoverable for 60 days.06 / What it costsBuild fee / managed platform
Two prices.
Both published.
The build fee covers the rebuild and comes down against a 24-month rails commitment. The managed platform fee covers hosting, operations, uptime, patching and peak-season scaling, every month after launch. Both are quoted in writing before anything is built.
Build fee$0 to $15k
Rails commitment24 months
Managed platform / monthly$2,000 to $4,000
Rollback window60 days
07 / Conversion guaranteeBeat it
Beat it
or reverse it.
If the rebuilt checkout does not beat your current conversion rate within 60 days, we roll it back and the build fee is not paid.
Start a processing review↗08 / Operated after launchNot a handoff to a theme shop
Checkout
Pre-purchase and post-purchase upsells your current checkout will not allow.
Uptime
Hosting and operating responsibility stay with us, not with you.
Patching
The stack is maintained after the cutover, every month it runs.
Peak scaling
The store is prepared for your traffic peaks before they arrive.
STORE / HANDOFF
RAILS
Once the checkout is yours, the money it takes has to land somewhere. The next layer is the account it lands in, how it routes between accounts, and how you get your data out.
Open RAILS↗Build beside it. Shift deliberately.
Twelve migrations completed. All twelve still trading.
Start a processing review↗