At the Dual Version deployment and provisioning stage, the source system's database is copied to the target system. Customers are then transferred in batches, so until the migration is complete, some customers are served by the source system and others by the target system.
Certain data, such as DID numbers and SIM cards, continue to change during migration and must remain consistent across both systems. To achieve this, changes are automatically synchronized. For example, when a SIM card is assigned on one system, its status is updated on the other system, preventing the SIM card from being assigned twice.
The following table shows which entities are synchronized, in which direction, and how changes are reflected on the other system.
| Entity | Direction | How changes reach the other system |
| DID numbers and DID pricing batches | Both ways (source ↔ target) | Automatically, usually within seconds |
| SIM cards (including custom field values) | Both ways (source ↔ target) | Automatically, usually within seconds |
| Rates and destinations | From source to target only
(manage these entities on the source system) |
Automatically, usually within a minute |
| Call recordings | From source to target only | Automatically, within an hour (hourly by default) |
| Vendor xDRs and balances | From source to target only | Upon request, once per billing environment, after all its customers and resellers have been transferred. Decide whether you need it during the pre-migration analysis. |
Automatic synchronization is set up during the Dual Version deployment and provisioning stage. No action is required from your team.
DID numbers and DID pricing batches
The source and target systems maintain their own copies of the DID number inventory. To maintain consistency and prevent the same number from being assigned on both systems, DID numbers are synchronized in both directions:
- When you add a DID number on one system, the same number is added on the other system.
- When a DID number is assigned/unassigned to an account or allocated to a customer on one system, it is marked as unavailable on the other system.
- When a DID number is no longer assigned to any account or customer on one system, it becomes available on the other system too.
- When a DID number is removed from the DID inventory on one system, the other system immediately marks it as unavailable.
That number's record stays in the database until a daily cleanup task removes it. The task deletes a number only after at least one day has passed since the removal and all charges for the number up to the removal date have been applied. Once the first system deletes the number from its database, the other system deletes it as well.
DID pricing batches, including their markup settings, are also synchronized to keep DID pricing consistent across both systems.
Each DID number exists on both systems, but incoming calls to this number are delivered to only one of them. The forwarding registry records which system (source or target) receives the calls for each assigned DID number (see Call delivery in Dual Version PortaSwitch).
- Assigned DID numbers. When you assign a DID number on either system, the forwarding registry is updated automatically, so calls to that number go to the system where it is assigned. When Porter transfers a customer to the target system, the registry is updated for that customer’s DID numbers as well.
- Free (unassigned) DID numbers. A DID number that isn’t assigned to any customer or account has no entry in the forwarding registry, so customer transfers don’t affect it. Incoming calls to free DID numbers are routed to the fallback system, which is the source system during migration (see Fallback call delivery).
- Switching free DID numbers after migration. Once all customers in a billing environment have been transferred, PortaOne Support switches that environment’s free DID numbers to the target system. The forwarding registry then directs incoming calls for these numbers to the target system. On the source system, the numbers are marked as “In use” and can no longer be assigned. This step is mandatory for each billing environment.
SIM cards
The source and target systems maintain their own copies of the SIM card inventory. To keep them consistent and prevent the same SIM card from being assigned on both systems, SIM cards are synchronized in both directions:
- When you add/delete a SIM card on one system, the same SIM card is created/deleted on the other system.
- When a SIM card is assigned to an account or allocated to a customer, distributor, or representative on one system, it is marked as "In use" on the other system and can't be assigned there.
Assignment details (which account, customer, distributor, or representative the SIM card is associated with) are not synchronized. For example, if a SIM card is allocated to a customer on the source system, the target system shows which customer the SIM card is allocated to only after Porter transfers that customer.
- When a SIM card becomes available on one system (i.e., it is no longer allocated to any customer, distributor, or representative), it also becomes available on the other system.
When a SIM card is released from an account, it remains allocated to the account’s customer, so it remains “In use” on the other system.
The values of built-in SIM card fields, including PIN, PUK1, PUK2, activation code, activation date, and disposal date, are synchronized when a SIM card is created and whenever these values change. A field is synchronized only if it is supported by the releases of both systems.
The values of custom SIM card fields are also synchronized when they are added, changed, or removed, if:
- The source system runs MR110 or later.
- The custom field was copied from the source to the target system during the initial database copy. Custom fields are subject to the product catalog freeze, so fields added during the migration aren’t synchronized.
Rates and destinations
While most product catalog entities can't be changed during Dual Version migration, rates may need to be updated, for example, when a vendor changes its prices. You can continue updating rates on the source system and the changes are automatically synchronized to the target system. This ensures that customers are charged consistently, whether they are still on the source system or have already been transferred to the target system.
The following changes are synchronized from the source system to the target system:
- Rates – adding, updating, and deleting rates in tariffs that exist on both systems.
- Destinations – adding, updating, and deleting destinations, so that rates for new destinations can be applied on both systems.
Tariffs themselves are not synchronized and are subject to the product catalog freeze. On the target system, you can modify rates only for tariffs created there. For details, see Entity change restrictions during migration.
Call recordings
If call recording is configured, new recording files are automatically copied from the source system to the target system, so customers can access their recordings after being transferred. Synchronization runs once an hour by default, so a recording made on the source system may take up to an hour to appear on the target system.
Synchronization works in one direction only: recordings made on the target system are not copied to the source system.
Vendor xDRs and balances
After the database is copied, the same vendor exists on both systems. From that point on, vendor balances change independently: calls processed by the source system affect the vendor balance there, while calls processed by the target system affect the balance on the target system. To reconcile a vendor’s invoice during migration, use the xDRs from both systems.
If you need combined historical data and accurate vendor balances, PortaOne Support can synchronize vendor data once, at the end of the migration. For each vendor, this one-time synchronization:
- Transfers the vendor xDRs created on the source system after the database has been copied to the target system.
- Adds the charges from these xDRs to the vendor balance on the target system.
- Regenerates the vendor xDR reports created after the database has been copied.
To make this synchronization possible:
- Keep xDRs long enough. The xDR retention period on both systems must cover the whole migration – from when the database is copied until the source system is decommissioned. Retention is set by the CDR.Keep_month option on the Configuration server web interface.
- Transfer all customers and resellers first. Synchronization runs per billing environment, only after all its customers and resellers have been transferred and the source system no longer produces new xDRs for the vendor.
Vendor configuration is not synchronized. See Entity change restrictions during migration for which vendor changes are allowed on each system.
Synchronization after migrating a billing environment
If your system has several billing environments, some of them may be fully migrated to the target system while others are still in progress. Once a billing environment has been fully migrated, continued synchronization of DID numbers, SIM cards, and call recordings is no longer needed and may cause issues:
- After migration, restrictions on modifying entities in the billing environment can be lifted. You can again modify entities that aren't synchronized between the systems, such as DID vendor batches. However, changes to DID numbers that reference these entities can't be synchronized and trigger monitoring alerts.
- The source system also no longer generates call recordings for the migrated billing environment. Synchronization therefore has no new recordings to copy and only adds unnecessary load to both systems.
For these reasons, PortaOne Support disables synchronization of DID numbers, SIM cards, and call recordings for each billing environment once its migration is complete.