Preparation steps

The pre-migration analysis (PMA) is required to ensure that the Dual Version migration will go smoothly, so it is a mandatory step for any Dual Version migration project. During this analysis, we check a number of things, including:

• External components your system is integrated with, and peculiarities in сonnecting those systems to PortaSwitch that need to be addressed
• Custom code or other modifications you might have on your source system, and how to replicate all of those modifications to ensure that the new version of PortaSwitch functions smoothly
• Custom reports you use, as they also might need to be adapted to work on a new PortaSwitch version
• And more. Find more information about the PMA stage here.

Pre-migration analysis (PMA) typically takes about two weeks (10 business days). Investing these two weeks upfront can save you months of potential delays during the migration process!

Dual Version setup includes the target system preparation, Dual Version deployment and provisioning (making two systems – source and target – operate in parallel), and all other steps that should be completed before customer migration.

The Dual Version deployment and provisioning process is fully automated. In a PortaOne testing lab, the full preparation process would only take a few days. In practice, the timeframe may extend to approximately one month between installing your target system and the first test of migrating your customers. Let’s look at a more detailed breakdown of this process:

• Performance testing: After the target system is installed, the PortaOne team tests its performance.
• Scenario Testing: As the owner of the target system, you will need to further conduct a series of tests on all the main scenarios you are currently using in production.
• Reconfiguration and database copying: Subsequently, both the source and target systems undergo reconfiguration, and all the databases are copied from the source (current) system to the target (new) one. Depending on the database size and need for the task and time slot coordination, this process may take a few or more days. Then, these systems are linked together.
• IP address switching: Finally, we will switch the IP addresses from the source system to the dispatching SBC that is located on the target system.

Since these activities are performed on the live system, reconfiguration is usually scheduled during off-peak hours to minimize disruptions. All of these activities need to be thoroughly planned. This is why, in the real-life scenario, the Dual Version setup usually takes about a calendar month.