Migrating PPPoE Subscribers Without Rewriting Paid Time

WayaDesk / PPPoE and renewals

Migration should preserve what customers have already purchased. It is not an opportunity to restart every subscription or count imported entitlement as new revenue. Begin with an export and a clear mapping between old records and the intended new accounts.

Inspect a small sample first

Use representative records: an active customer, an expired customer and an account with an unusual service date. Confirm how identifiers, credentials, packages and expiry values are represented. Keep original files unchanged so you can explain any transformation.

Validate entitlement and authentication separately

A correctly imported date does not prove the subscriber can log in. Likewise, successful authentication does not prove the imported period is right. Compare both with the source record during a controlled pilot.

• Resolve duplicate identifiers before importing the full customer base.
• Check timezone interpretation and exact expiry values.
• Keep imported service records separate from payment reporting.

Avoid two competing controllers

Plan when the old system stops controlling the selected customers and when the new installation takes responsibility. Do not let both systems independently apply expiry or provisioning decisions to the same network without an explicitly designed transition.

Retain a rollback decision

Write down the conditions under which you will return to the old arrangement and how new payments during the transition will be reconciled. A migration is complete when customer service and records have been verified, not when an import process reports that it finished reading a file.