> ## Documentation Index > Fetch the complete documentation index at: https://docs.upmind.com/llms.txt > Use this file to discover all available pages before exploring further. # Planning Your Migration Strategy > A phased approach to migrating from Cart 1.0 to Cart 2.0 safely, with a full pre-launch checklist to validate before going live. * **Time** — 15 minutes * **Difficulty** — Intermediate **What You'll Learn:** A structured migration plan covering parallel running, sandbox testing, gradual rollout, and rollback steps, plus a complete checklist across products, pricing, promotions, taxes, theming, and more, so your team can switch to Cart 2.0 with confidence and minimal risk to live customers. **Prerequisites:** * An active [Upmind account](https://upmind.com/start) currently running Cart 1.0. * A read-through of [Understanding the Migration Overview](/using-cart-20/migrating-from-cart-10-to-cart-20/understanding-the-migration-overview) to understand the scope of changes before planning your approach. * Awareness of your current storefront setup, including products, pricing rules, promotions, tax configuration, and any active integrations or webhooks. * Access to a sandbox environment for pre-launch testing. * [Upmind Support](https://upmind.com/support) contact details in case rollback assistance is needed. A phased migration approach reduces risk, protects revenue, and allows teams to validate Cart 2.0 with confidence before fully switching live traffic. Rather than treating migration as a single cutover event, this strategy breaks the process into controlled stages that allow testing, observation, and rollback at each step. ## The Strategies ### Step 1: Parallel run A parallel run allows Cart 2.0 to be validated alongside Cart 1.0 without disrupting live customers. * **Cart 1.0 remains live during migration:** Existing checkout flows continue to operate normally while Cart 2.0 is prepared and verified. * **Cart 2.0 is enabled by Upmind as part of the migration process:** No changes are required from the customer unless explicitly requested. * **Behaviour can be validated without impacting customers:** Teams can review flows, pricing, and presentation before any traffic is switched. If a team chooses to use a separate checkout subdomain, a parallel URL can be provided for additional validation. This is optional and typically used for internal testing or stakeholder review, rather than a required migration step. ### Step 2: Sandbox testing Sandbox testing ensures that all commerce behaviour works as expected before exposing Cart 2.0 to live traffic. * **Use test products and payment gateways:** This allows teams to simulate full checkout flows without creating real orders. * **Validate pricing, taxes, promotions, and edge cases:** Special cases such as discounts, trials, and region-specific pricing should be reviewed. * **Confirm behaviour across devices and regions:** All device experiences should be tested with different locales and currencies. ### Step 3: Gradual rollout A gradual rollout reduces risk by introducing Cart 2.0 to real traffic in a controlled way. * **Monitor conversion, errors, and customer feedback:** Early signals help confirm that the new experience performs as expected. * **Expand usage once confidence is high:** Traffic can be increased once key metrics remain stable. ### Step 4: Rollback plan A clear rollback plan ensures that any issues can be resolved quickly and safely. * **Cart 1.0 configuration remains unchanged during migration:** This allows a reliable fallback at any point. * **Switching between Cart 1.0 and Cart 2.0 is managed by Upmind:** Customers do not need to manage routing or configuration changes. * **Reverting to Cart 1.0 can be done quickly with Support assistance:** Rollback does not require data changes or reconfiguration. No DNS or routing changes are required from the customer unless they have opted into a custom checkout subdomain. ## Migration checklist This checklist helps teams confirm readiness before go-live and reduces the risk of missed details. It should be reviewed during sandbox testing and again before switching to live traffic. ### 1. Products Confirm that the catalogue appears and behaves correctly in Cart 2.0. * All products are visible and ordered correctly in the catalogue. * Product descriptions, images, and labels are accurate. * Configuration steps render and validate as expected. ### 2. Pricing Ensure pricing behaviour matches existing expectations. * Billing cycles and renewal terms match the current setup. * Discounts, trials, and introductory pricing apply correctly. * Zero-price or free products display and behave correctly. ### 3. Promotions Validate that promotional logic carries over cleanly. * Promo codes validate and apply correctly. * Stacking rules and exclusions behave as expected. * Labels and badges display consistently across screens. ### 4. Domains Review domain-related flows where applicable. * Domain search and purchase flows work end to end. * Pricing and availability are accurate. * Existing domain paths resolve correctly. ### 5. Taxes Confirm tax handling across regions. * Inclusive or exclusive tax display is correct. * Regional tax rules calculate as expected. * Tax line items appear correctly in the basket and checkout. ### 6. Webhooks Verify downstream integrations. * Order and payment events fire correctly. * Connected systems receive updates as expected. * Retry and failure behaviour is confirmed. ### 7. Analytics Ensure visibility into performance and conversion. * Page views and conversion events are tracked. * Funnel steps are mapped correctly. * Any custom events are validated. ### 8. SSO Confirm authentication behaviour if applicable. * Login and account linking work correctly. * Sessions persist across checkout steps. * Redirects behave correctly after checkout completion. ### 9. Theming Review the final presentation across devices. * Brand colours and typography are applied correctly. * Device layouts are visually consistent. * Accessibility, contrast, and readability are checked.