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

# Migrating from TWICE 1.0

> The sequence that takes a merchant from a migrated 2.0 account to 1.0 being switched off.

Your catalog and inventory have been migrated into TWICE 2.0. This path covers everything you do from there until 1.0 is switched off.

Nothing else has moved, and nothing has been switched over — **1.0 is still taking your orders.** Work through the steps in order. Steps 1 to 7 happen before you switch, step 8 is the switch, and step 9 runs both systems down.

If you are setting up a new account rather than migrating one, follow the [launch path](/docs/guides/launch/overview) instead. The two overlap, but a migration has a live system on the other side of it and a launch does not.

## Two rules that hold throughout

Everything else in this path is a task. These two are constraints — break either one and you get double-sold stock or money you cannot reconcile.

<Warning>
  **Only one system takes new orders.** Collections and returns run in both systems at the same time, and that is fine. Taking new orders in both is not: the same stock item can be sold twice.
</Warning>

<Warning>
  **1.0 keeps everything made before the switch.** Orders, deposits, saved cards and order history stay in 1.0. Keep 1.0 running until the last of them is closed — which, if you take bookings dated months ahead, is later than you think.
</Warning>

## The nine steps

<CardGroup className="doc-rows-numbered">
  <Card title="Check what was migrated" href="/docs/guides/migration/check-what-was-migrated">
    Done when: your counts and prices reconcile against 1.0, and anything that did not has an owner.
  </Card>

  <Card title="Configure settings" href="/docs/guides/migration/configure-settings">
    Done when: every settings view has been opened and either configured or confirmed as not needed.
  </Card>

  <Card title="Connect payments" href="/docs/guides/migration/connect-payments">
    Done when: a live-mode payment has been taken and refunded.
  </Card>

  <Card title="Move your subscription" href="/docs/guides/migration/move-your-subscription">
    Done when: your trial has started and your 1.0 subscription shows as canceled.
  </Card>

  <Card title="Test your processes" href="/docs/guides/migration/test-your-processes">
    Done when: your own people have run every case, unaided, and seen the customer-facing output.
  </Card>

  <Card title="Set up and train your team" href="/docs/guides/migration/set-up-and-train-your-team">
    Done when: every user has the right role and each location has a named superuser for the switch.
  </Card>

  <Card title="Clear the external dependencies" href="/docs/guides/migration/clear-external-dependencies">
    Done when: your store address is live, integrations are repointed, and 1.0 exports are stored outside TWICE.
  </Card>

  <Card title="Switch new orders to 2.0" href="/docs/guides/migration/switch-new-orders">
    Done when: every 1.0 intake channel is closed and you have placed a real transaction in 2.0.
  </Card>

  <Card title="Run both systems until 1.0 is finished" href="/docs/guides/migration/run-both-systems-down">
    Done when: the last pre-switch order is closed and your records are stored outside TWICE.
  </Card>
</CardGroup>

## If you do not take bookings

Several steps here exist because a booking is made on one date and fulfilled on another: running both systems down, blocking stock that is out on a 1.0 booking, releasing deposits from the 1.0 order. If everything you sell is fulfilled at the moment of sale, those steps are short — you still work through them, but 1.0 empties in days rather than seasons.

Where a step turns on that difference, it says so.

## What is not in scope

This path covers what moves by default. Anything else moves only if it was agreed in your migration scope — confirm that with your TWICE contact rather than assuming.

The path also does not explain how each area of TWICE works. Where a step needs that, it links to the guide or concept page that covers it, so the sequence stays readable.

## Related articles

<CardGroup cols={2} className="doc-rows-condensed">
  <Card title="Launch path" href="/docs/guides/launch/overview">
    The same sequence for a new account rather than a migrated one.
  </Card>

  <Card title="TWICE Commerce overview" href="/docs/twice-commerce-overview">
    What the platform does and how its pieces fit together.
  </Card>
</CardGroup>