Migration guide
CoinPayments Legacy Migration Planning Guide
Plan a CoinPayments Legacy migration by mapping dashboards, credentials, IPN callbacks, API endpoints, plugins, payment statuses, and support scripts.
CoinPayments Legacy migration is the process of moving an older CoinPayments account, plugin, or IPN workflow to a newer integration model without breaking checkout, fulfillment, or accounting. The safest migration starts with inventory, not code.
Key takeaways
- Identify the current dashboard and API model before changing settings.
- Preserve a copy of legacy IPN payload examples and order status mappings.
- Test new callbacks with real internal orders before customer launch.
- Keep old and new support scripts available during the transition.
Inventory the current setup
List the store platform, plugin version, callback URL, API credentials, supported assets, settlement settings, and every internal system touched by payment state. Many legacy migrations fail because an old accounting export or support script was forgotten.
Map statuses before launch
Legacy status names may not match the new integration exactly. Create a table that maps gateway statuses to internal order states. Then review each state with fulfillment, support, and finance.
Run parallel tests
Use a controlled test order to compare legacy behavior with the new workflow. Capture payment creation, callback receipt, order update, customer email, and reconciliation output.
Migration decision
Migrate when the new workflow handles happy-path and abnormal cases. Delay if underpayment, overpayment, expiration, or refund states are unclear. A slow migration is cheaper than a broken checkout.