Migration guide

Off your stack. Into ours. In a weekend.

The honest version. What we migrate, what we don't, what a typical timeline looks like, and what our migration team actually does for you.

From Shopify (or Shopify Plus)

You can sit alongside Shopify (recommended) or replace the checkout layer entirely. Most brands keep Shopify as the product catalog + storefront, and run GrowthFlowLine for checkout, payments, CRM, and subscriptions.

  • Products + variants: one-way sync, hourly. We do not duplicate inventory.
  • Customers + addresses: full import on day 1. Deduped by email.
  • Historical orders: 24-month default. Older on request.
  • Discount codes + tax rules: one-click import.

From Recharge

This is the hairiest piece — recurring tokens, retry schedules, customer portal links. Our migration team has done this 400+ times. The short version:

  1. We re-tokenize subscriptions on your new processor without re-prompting shoppers (vault-to-vault transfer where supported, OAuth re-auth where not).
  2. Existing renewal dates are preserved to the day. Dunning state is preserved (retry count, last failure code).
  3. Customer-portal URLs from Recharge redirect to your new portal for 90 days.
  4. No re-billing customers during the cutover window. We freeze billing on Friday, cut over Saturday, resume Monday.

From Gorgias (or Zendesk / Front)

Conversation history imports cleanly. Macros and rules get mapped to our equivalents — we'll review every one with your CS lead. Channel re-connection (Gmail, SMS, IG, chat) is a 30-minute task per channel.

Stripe-only setups

If you're running Stripe Checkout or Stripe Payment Element today, we connect your Stripe account directly. No data leaves Stripe — you keep the same merchant ID, the same payouts, the same dashboard. We add routing, dunning, and the rest of the platform on top.

Custom builds

If your checkout / subs / CS layer is custom-built, our solutions team will scope a 2-3 week migration project at no cost. Most custom builds reuse 80%+ of their existing storefront and product data — we layer the GrowthFlowLine engine underneath.

A typical timeline

  • Week 0 Kickoff call. Scope, map fields, decide cutover window.
  • Week 1 Data import (products, customers, orders, subs). Staging workspace is live.
  • Week 2 Checkout build + A/B test against current. Processors connected. CS macros migrated.
  • Cutover Friday evening: billing frozen. Saturday: DNS / iframe swap. Monday: live, supported.
  • Week 3 Daily check-in. Tuning routing, dunning, automations. Decommission old apps.

Our migration team

Every migration gets one solutions engineer + one CS lead, working in your Slack from kickoff to 30 days post-cutover. No tickets, no hand-offs. Free on every plan.

Plan your move

Tell us what you're on. We'll tell you exactly how long.

20-minute call, no slide deck. We map your stack and give you a date.

20-min call Weekend migration Real operators