Foundation · 2 min
What you need to know
Does an ecommerce migration need a rollback plan?
Yes. A rollback plan defines triggers, authority, time limits and data reconciliation, so a failed launch does not become an improvised recovery.
What should trigger a migration rollback?
Trigger rollback when a predefined critical condition, such as unsafe payments, unrecoverable orders, severe data corruption or prolonged unavailability, exceeds its threshold and cannot be corrected inside the launch window.
How long should rollback remain possible?
Keep rollback possible only while reversal remains safer than forward recovery, and new transactions can still be reconciled. Set the deadline before launch using volume, data-change and recovery constraints.
How should new orders be handled if a rollback occurs?
Preserve every new order with its payment, inventory and customer state, then import or process it in the restored system exactly once. Communicate delays without asking customers to reorder blindly.
How should data created after cutover be reconciled after rollback?
Extract all post-cutover changes using stable identifiers and timestamps, classify conflicts and apply an approved merge order. Reconcile orders, payments, customers, inventory and entitlements before declaring rollback complete.
A quick store check
Simulate one rollback decision and prove that post-cutover orders, payments and inventory changes remain recoverable and reconcilable.
Foundation · 2 min
Frequently asked questions
Is rollback always safer than fixing forward?
No. After enough new activity, reversal may create greater data risk. Define a time limit and decision criteria.
Can rollback restore data automatically?
Infrastructure reversal may be automated, but business transactions still require controlled reconciliation.