Migration Validation
What Is Migration Validation?
Migration validation compares source data and approved migration requirements with the configuration built on the destination platform, allowing discrepancies and exceptions to be reviewed before cutover.
Validation vs. post-cutover verification
Migration validation | Post-cutover verification | |
|---|---|---|
When | Before live traffic moves | After customers move |
Question it answers | Was everything built correctly? | Does everything work under live traffic? |
Typical method | Comparing source and destination data, reviewing exceptions, testing in a non-production environment where available | Test calls, device registration checks, monitoring tickets and call failures |
Outcome | A go/no-go decision for the wave | Sign-off and exit from the wave |
Both are needed. Validation catches configuration issues while they are still easy to fix; verification confirms service in production.
What does migration validation check?
Customer and account structure, such as domains, sites and resellers
Users, extensions and assigned features
Phone numbers and inbound routing
Call flows, including hunt groups, call queues and auto attendants
Voicemail settings and greetings within the agreed scope
Devices and their provisioning configurations
Features that need a different design, recorded as exceptions
E911 address records for each number
Billing references for migrated services and numbers
How does migration validation work in practice?
Compare. Check what was extracted from the source platform against what will be built on the destination platform, customer by customer.
Review exceptions. Flag settings that do not map directly and review them with the provider.
Test. Where available, build and review migrated configurations in a non-production environment before customers move.
Sign off. Confirm validation results against the go/no-go criteria for each wave.
Otto™, Vox Matic's proprietary automated telecom migration framework, applies automated validation checks throughout data extraction, transformation and provisioning, helping identify discrepancies for review before cutover. On a Metaswitch to NetSapiens migration, converted data is presented for review before anything is provisioned. Our NetSapiens migration data validation checklist covers the checks in detail.
Frequently asked questions
Can migration validation be fully automated?
Automated checks can compare large volumes of data consistently, but exceptions, design decisions and sign-off still need people. Validation works best as a combination of automated checks and engineering review.
When should validation start?
Before provisioning, when extracted data is first converted to the destination structure, and again before each wave's cutover. Issues found early are easier to correct.
What is the difference between migration validation and data integrity?
Data integrity is the goal: subscriber, routing and billing data that stays accurate and complete as it moves. Validation is one of the main ways that goal is checked.
Related terms
Validate before you move
See how Otto™ supports NetSapiens migrations.
NetSapiens is a trademark of Crexendo, Inc. Metaswitch and BroadWorks are trademarks of their respective owners. Otto™ and Forge™ are trademarks of Vox Matic. Vox Matic is an independent migration services provider. References to third-party products are for identification and interoperability purposes only and do not imply endorsement, except where an authorized partnership is expressly identified.