During the Dual Version deployment and provisioning stage, the source system's database is copied to the target system. After this initial copy is made, different types of data are handled differently during migration:
- Product catalog and other configuration data are not synchronized after the database is copied. Changes to the corresponding entities are restricted during migration: some entities such as service policies or taxation settings can be changed if you apply the same change on both systems. However, product catalog entities cannot be changed at all, a restriction referred to as “product catalog freeze”. See Entity change restrictions.
- Data that keeps changing and must stay up to date on both systems (e.g., DID numbers, SIM cards, and rates) is automatically synchronized during migration. See Entity synchronization.
- Customer-related data (customers, accounts, resellers, representatives) is copied to the target system as inactive. When the Porter tool transfers a customer batch, it synchronizes changes made after the database is copied, and from then on, the target system serves these customers. See Customer data transfer.