After all customers have been migrated and all traffic has been switched to the target system, the Dual Version migration is considered complete. Once the target system has been running successfully for a sufficient period (for example, 2–4 weeks or at least one billing cycle), the source system can be decommissioned. At this point, the target system operates independently as the primary system for all operations.
If the service provider is preparing the next migration “jump” (e.g., from MR100 to MR115) immediately or within the next few months, the DSBC components deployed specifically for the Dual Version migration will remain in place, and the former source system can be reused as a target system for the next migration. However, for each subsequent Dual Version migration, the source and the target systems should have the same number of DSBC components. See the recommendations for DSBC deployment here.
After the migration is completed, perform the following cleanup tasks regardless of whether the source system will be decommissioned or kept for a future migration:
- on the source system:
- disable the SIPForwarder handler in all the PortaBilling environments and
- clear the alert email settings in the Provisioning.AlertRecipient option on the Configuration server
- on the target system: clean up internal entities created for call routing
For assistance, contact the PortaOne support team.
