Legacy-Newborn Sync System

Depending on the size of the data to be migrated to the new system, our initial estimation was about 7 days time for the migration. This was not feasible.

The only solution was a Synchronization system that would pull all the data from the legacy system to the new system. After the complete pull, the system would then keep all of the data in sync as well with the legacy system. The following entities of the legacy system were programmed to be pulled and synced.

1. Providers
2. Providers' Users
3. Students
4. Courses
5. Students' course progress
6. Products
7. Orders
8. Coupon Codes
9. Purchase/Registration Codes
10. DL/ID Informations
11. User Credentials
12. Store Locations (for Prof. Demo. page)

Apart from the sync script, there are several operations that might be needed to be performed after syncing data, so we programmed scripts and interfaces for these actions as well.

1. User roles and capabilities patch ups
2. Activate providers
3. Manually assign wandering products to respective synced providers.
4. Manually assign parent products to imported products (for correct commission calculations as per the new system)
5. Manually assign exported store locations with corresponding Providers in the new system, as well as their opt-in settings. 
6. Manually assign redirect URLs so the providers' old store URLs redirect to their new URLs after going live.
7. Setting up the following in LTC Settings.