Syncing internal elements

The vendor configuration is duplicated in Dual Version PortaSwitch. This means that the same vendor is active on both the current (source) and new (target) systems. The balance of the vendor is split between the two systems since calls that go via the source system change the balance of the vendor there, and similarly for the target system.

If you need to, for example, reconcile a vendor’s invoice during the migration, it is important to remember this and to use the CDRs (also referred to as xDRs) from both systems. Your actual balance with your vendor will be the sum of the vendor balance from both systems.

If you like, when the Dual Version migration is finished, our PortaOne support team can synchronize your vendor xDRs using a dedicated tool.

• All entities that are created under a specific customer, such as uploaded music on hold, voicemails, invoice .pdf files, and so on, will be migrated to the new (target) system automatically using the Porter utility.
• For entities that reflect your business inventory and are changed quite frequently, such as rates, SIM cards, and DID numbers, there’s close to real-time automatic synchronization.
• Call recording files are synchronized with the target system using a dedicated script that is periodically launched on your source system.
• Entities like custom reports and invoice templates are not linked directly to the customer record, so they cannot be migrated by the Porter utility. However, these files are duplicated to the target system while copying the database on the Dual Version deployment stage, so there is no need to re-create them.
  If you need to make changes in your invoice template, a custom report, or create a new template/report, you should replicate these changes within the target system. Alternatively, you can wait until the migration is finished (all customer records are transferred to the target system, and the two systems are disconnected). Then you can manage these entities on the target system as your primary “current” system.

  This is one of the reasons why we have a mandatory Pre-migration analysis as a first step of every Dual Version migration. During this analysis, we will help you more accurately plan the changes according to your specific needs.

For Dual Version jumps starting from MR100, the invoice number generator supports “parity mode” by default to avoid duplicate invoice numbers. For example:

• For customers whose records are on the source system (haven’t been migrated yet), it will generate invoices with odd numbers, e.g., 715, 717, 719
• For customers whose records have been migrated to the target system, it will generate even numbers, e.g., 716, 718, 720