Free, no email required. Keep completed worksheets private. Do not include consumer contact details or recordings.
Inventory before changing anything
List tracking numbers, carrier arrangements, destinations, opening hours, campaign rules, integrations and report recipients. Identify the person who controls each account. Ask providers about porting and export limitations before promising a migration date. Preserve dated agreements and amendments separately from software settings.
Map records without mixing obligations
Give each buyer, publisher and campaign a private mapping between old and new identifiers. Reconcile prepaid allocations, earned charges, adjustments, disputes and supplier payables separately. Copying a cap or current dashboard total does not establish the opening financial balance.
Prove a bounded path
Use an authorized test environment to check the actual caller journey, unavailable destinations, duplicate callbacks, recording access and payment retries. Define which evidence must pass before a pilot. An administrator screen saying enabled is not delivery proof.
Keep a rollback decision
Record who can stop the pilot, how existing service will be restored and how calls in flight will be reconciled. Avoid changing several operational variables at once. Do not disconnect working service until the accepted transition requirements are met.
Close the reconciliation
Compare the same window and the same event definitions across systems. Investigate missing or repeated events before labeling a difference a loss. This checklist does not imply a RingFunnel migration service or supported integration is available; confirm current capabilities. Use the RFP worksheet to retain acceptance criteria.