Moving an SMM panel involves more than copying customer names. Wallet balances, open orders, service mappings and provider references need to agree after the move. A panel can look correct on the surface while an old order or customer balance is still wrong underneath.
ExcelPanel offers free migration assistance for users, wallet balances, orders and order history, services, and providers. The team needs to review your current platform and data before arranging the move. A supported data category is not a guarantee that every database format can be imported unchanged.
List the data you need to move
Start with the source platform, approximate account and order counts, and the data available for export. Identify customer identifiers, current balances, provider accounts, local service IDs and provider-side service IDs. Keep the original backup intact while the migration is reviewed.
- Users and the identifiers used to match their records.
- Wallet balances and the currency those values represent.
- Order history, including open orders and provider order references.
- Service settings, customer descriptions and provider mappings.
- Provider configuration that must be rechecked after transfer.
Agree a cutover before collecting the final export
Choose when the old panel stops accepting changes and when customers should use the new panel. Orders and deposits arriving after an export create a gap between the two systems. Decide with the migration team how that gap will be handled before switching your domain.
Do not assume a zero-downtime transfer. The cutover depends on your source system, data quality and operating requirements. Keep customer communication ready and avoid promising a completion time before the data has been reviewed.
Reconcile customer balances
Compare account counts and balance totals in the source snapshot with the imported result. Check individual accounts as well as the total, especially customers with recent deposits or adjustments. Confirm that currencies and decimal precision have not changed the meaning of a balance.
Keep a record of the snapshot time and any agreed adjustments. If a payment arrives during the move, it should have an identified destination and a review trail rather than being credited manually in both systems.
Review open orders and provider IDs
An order already sent upstream may continue running while your panel is moved. Retain its provider reference and check its state before resending it. A new local record does not make the upstream order a new order.
Verify the mapping between local services and provider services. Similar service names can hide different quantities, prices or conditions. Test a small new order after the move and check the response before reopening the full catalog.
Check customer access and the storefront
Agree how sign-in and account recovery will work after migration. Password storage differs across systems, so do not assume a source password format will work without review. Test customer accounts using the agreed access process.
Then check your domain, branding, public pages, service descriptions and support routes. Review the payment configuration separately: transferring payment history is different from confirming that a merchant account and callback work on the new panel.
Complete a post-migration check
Before inviting customers back, verify a deposit, a customer charge, a new order and an order-status update. Check a sample of old history, outstanding tasks and reseller pricing. Keep the source backup and agreed reconciliation records available while early activity is monitored.
Contact the migration team on WhatsApp with your current platform details. For the new subscription’s order ranges and renewal rules, use the current pricing page.
