A second, no-code route — connecting an AI assistant and supervising while it does the typing — is planned, but isn’t available yet: AI connectors are read-only during the limited rollout, so they can’t create records. See Migrating your data with an AI assistant for why and what’s coming.
What can move
The three habits of a good migration
- Tag everything with its old ID. Every resource accepts free-form metadata; putting each record’s legacy ID there makes imports safely re-runnable, makes old→new lookups trivial, and means you can always trace any record to its source.
- Start small, verify, then scale. Ten patients first. Check them in the app — names, numbers, dates. Then the rest. Every issue caught at ten is an issue the other five thousand never have.
- Import facts, not conclusions. Send invoices, payments and allocations — not balances. PracticeHub derives balances from the records, so they’ll match your old system because they’re computed from the same facts.
What imported data looks like afterwards
Every record written through the API is labelled with its origin: attributed to the API key that created it, and marked as API-sourced in ledgers and activity views. Your team can always tell a migrated record from one typed in by hand — and with legacy IDs in metadata, always tell which record it was.Where to start
- Data migration over REST — shapes, ordering, idempotency, verification and throughput.
- Your old system’s export (CSV / Excel) is step zero. Get that first; everything else follows.