Before importing, list every source of truth: subscriber sheets, payment books, records in the head of your longest-serving technician. Decide which is authoritative for what — an account number, a phone, a service address — and what to do when sources disagree. Conflicts you resolve now never chase you later.
Agree the scope: customers only this month, services next, historical payments after that. Scope creep is the number one reason migrations stall.
Deduplicate phone numbers and account names before import. Decide blocking rules for conflicts (latest record wins, or every conflict reviewed). Take account balances as of a fixed cutoff date — never 'today' — so the numbers don't keep moving under you while you work.
The import itself should land in a staging pass you can inspect, then commit once it checks out.
After the move, run the first full billing cycle and reconcile it against your old books end-to-end. Keep the old source accessible — read-only — for at least one full cycle, so 'how did we do it before?' has a definitive answer while the team learns the new system.
The checklist closes when a renewal, a reconfigured device, and a disputed payment can each be answered from the new record alone.
Resources
This guide covers the approach — the platform is where you run it day to day.