> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macropay.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate to Macropay

> Move off Lemon Squeezy, Paddle, or Stripe Billing with zero downtime — and become a merchant of record on day one.

Most billing migrations stall on the same fear: that a botched cutover will
drop active subscriptions, force every customer to re-enter a card, or punch a
hole in your tax records. Macropay migrations don't work that way. We move your
catalog, customers, and live subscriptions into a sandbox first, you sign off on
it, and only then do we flip the switch. Your customers' next invoice simply
arrives from Macropay — same card, same renewal date, same price.

And because Macropay is a **merchant of record**, the moment you cut over we
become the legal seller. We remit sales tax and VAT worldwide, absorb PCI scope,
and own chargeback handling — so migrating isn't just a platform swap, it's
offloading your tax and compliance liability in one step.

<Card title="Kick off your migration" icon="rocket" href="mailto:sales@macropay.ai?subject=Migrate%20to%20Macropay&body=Hi%20Macropay%20team%2C%0A%0AWe%27d%20like%20to%20migrate%20to%20Macropay.%0A%0ACurrent%20platform%3A%20%28e.g.%20Lemon%20Squeezy%20%2F%20Paddle%20%2F%20Stripe%20Billing%29%0AApproximate%20number%20of%20active%20subscriptions%3A%0AApproximate%20monthly%20revenue%3A%0ATarget%20cutover%20date%3A%0A">
  Email **[sales@macropay.ai](mailto:sales@macropay.ai)** and you'll get a migration plan plus a dedicated
  Slack channel for the cutover within one business day.
</Card>

## A managed migration, not a DIY export

You don't script anything. Send us read access to your current platform and our
team handles the import and reconciliation end-to-end — products, prices, live
subscriptions, license keys, files, and discount codes all land in Macropay
matched against your source data before any customer sees a change.

<CardGroup cols={2}>
  <Card title="Product catalog" icon="box-open">
    Products, prices, billing intervals, trial windows, and metadata — mapped
    into Macropay's unified product model.
  </Card>

  <Card title="Customers" icon="users">
    Profiles, billing addresses, tax IDs, custom fields, and marketing
    consents move with the account.
  </Card>

  <Card title="Live subscriptions" icon="arrows-rotate">
    Current cycle, next charge date, prorated credits, and coupon state all
    carry over — no re-billing, no gaps.
  </Card>

  <Card title="License keys" icon="key">
    Issued keys and their activation status transfer intact. Nobody re-activates
    a thing.
  </Card>

  <Card title="Downloadable files" icon="file-arrow-down">
    Re-uploaded to Macropay storage with fresh signed URLs behind your
    entitlements.
  </Card>

  <Card title="Discounts" icon="tag">
    Active codes, redemption counts, and expiry rules come across as configured.
  </Card>
</CardGroup>

## The four-step cutover

<Steps>
  <Step title="Discovery call">
    A 30-minute call to inspect your platform's export format, your custom
    plumbing (webhooks, integrations, custom fields), and your cutover
    constraints — peak traffic windows to dodge, time-zone considerations,
    launch dependencies.
  </Step>

  <Step title="Sandbox rehearsal">
    We replicate your full catalog and customer base into a Macropay
    [sandbox](/integrate/sandbox) account. Run test checkouts, click through the
    customer portal, and verify every price and subscription before anything
    customer-facing moves.
  </Step>

  <Step title="Go live">
    On the agreed date we run the live import, repoint your checkout URLs, and
    cut over your domain DNS. From that moment Macropay is the merchant of
    record and starts remitting tax on your behalf.
  </Step>

  <Step title="Two weeks of hands-on support">
    We stay in your Slack channel for two weeks post-cutover, triaging anything
    that surfaces and tuning your [webhook](/integrate/webhooks/events) consumers and
    reporting as you settle in.
  </Step>
</Steps>

## How each source platform maps

<Tabs>
  <Tab title="Lemon Squeezy">
    We combine the Lemon Squeezy CSV export with their API — the CSV alone omits
    current billing state, so we pull active subscriptions and license keys via
    the API to capture next-charge dates and renewal status.

    **Active subscriptions survive the move.** Customers keep paying without
    re-authorizing, because payment methods are re-keyed from your Lemon Squeezy
    exports into our PCI-compliant vault.
  </Tab>

  <Tab title="Paddle">
    Paddle's subscription-export endpoint already carries full billing state, so
    the mapping is clean. Paddle products and plans map onto Macropay's product
    and price model 1:1.

    **Active subscriptions survive the move**, with the same payment-method
    re-keying used for Lemon Squeezy.
  </Tab>

  <Tab title="Stripe Billing">
    Running raw Stripe Billing and want the merchant-of-record layer — tax
    remittance, dispute handling, payouts, KYC — without rebuilding billing? We
    import from your Stripe customer and subscription exports.

    Stripe-issued payment methods are re-used directly, so there's no
    customer-facing re-authorization step.
  </Tab>

  <Tab title="Other (Gumroad, Chargebee, Recurly, …)">
    Any platform with a structured export — CSV, JSON, or API — is fair game.
    Name your source in the email above and we'll confirm the approach and
    timeline before you commit to a date.
  </Tab>
</Tabs>

## What stays behind on purpose

Three things don't auto-transfer, by design:

| Item                       | What happens                                                                                                                                                                                                       |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Webhook subscribers**    | Repoint your consumers at Macropay's [webhook endpoints](/integrate/webhooks/events). Our event shapes resemble Stripe and Paddle but aren't identical — we help you map the payloads during post-cutover support. |
| **Historical tax filings** | Prior-period filings stay with your old platform. Macropay's tax record begins at the cutover date — clean ledgers, no overlap.                                                                                    |
| **Old invoice PDFs**       | Existing invoices remain at their original URLs on the source platform. New invoices are issued by Macropay from cutover forward.                                                                                  |

<Tip>
  Migrating an AI product or agent? Cutover is also the moment to switch on
  usage- and outcome-based billing. Point your app at the OpenAI-compatible
  proxy (`POST /ai/v1/chat/completions`) to capture token cost automatically, or
  send agent activity and outcomes to the [Signals API](/api-reference) — token
  spend that was invisible on your old platform becomes billable and traceable
  on day one.
</Tip>

## Common questions

<AccordionGroup>
  <Accordion title="How long is the actual cutover?">
    The live import runs in under an hour for accounts with up to roughly 10,000
    active subscriptions. The full arc — discovery to sandbox to cutover —
    typically spans one to two weeks, gated mostly by your launch readiness
    rather than our processing time.
  </Accordion>

  <Accordion title="Will my customers notice the switch?">
    Two things change on the receipt: **Macropay** now appears as the merchant
    of record on the customer's statement, and the support email updates. The
    card on file, the renewal date, and the price are all preserved.
  </Accordion>

  <Accordion title="Is there a migration fee?">
    No. Migrating to Macropay is free for every merchant. Our
    [pricing](/features/finance/balance) is purely per-transaction, so we earn over the
    customer lifetime — there's no upfront fee to nickel-and-dime.
  </Accordion>

  <Accordion title="What if my platform doesn't export a specific field?">
    We've moved merchants off most major platforms, so edge cases are familiar
    territory. If something in your data is genuinely unexportable, we'll flag it
    on the discovery call and tell you straight whether we can move it or whether
    you'll recreate it manually in Macropay.
  </Accordion>
</AccordionGroup>

***

<Card title="Ready to map your cutover?" icon="envelope" href="mailto:sales@macropay.ai?subject=Migrate%20to%20Macropay">
  Email **[sales@macropay.ai](mailto:sales@macropay.ai)** and we'll book a discovery call within one
  business day.
</Card>