The migration checklist practices actually use
Migrations don't fail at the database — they fail at the details nobody owned. This checklist assigns every detail a phase and an owner.
The approach
Before signing: data inventory itemised in writing · migration owner named on both sides · term/notice dates on your current contract confirmed · integrations audited (claiming terminals, imaging, accounting) · exit rights in the new contract read. Before cut-over: full data verified against source counts · balances reconciled to the cent · staff trained on real migrated data · templates and sequences rebuilt · patients told if contact channels change. Cut-over weekend: final delta migrated · old system to read-only · claiming and payments tested live · Monday's first appointments confirmed working. First fortnight: daily reconciliation checks · a snag list with an owner · legacy export archived securely. Intellicore onboarding walks this exact list with you — that's the point of it.
Common questions
Is Intellicore built for Australian practices?
Entirely. Australian company (Intellisys Core Pty Ltd, Queensland), data hosted in AWS Sydney with one isolated database schema per practice, Privacy Act-aligned compliance posture, GST-compliant invoicing, and Medicare, DVA and health-fund claiming modelled end to end.
How does Intellicore pricing work?
Pricing is quoted per practice after a demo, and onboarding is done for you — our team installs, configures, migrates your data and trains your staff. There is no self-serve signup: every practice goes live with its data and workflows in place rather than an empty account.
How do I see it working?
Book a demo — we'll walk through Intellicore configured for your kind of practice, with your workflows. Use the form on this page and we'll reply to arrange a time that suits your team.
See it working with your kind of data
Register your interest and we'll arrange a walkthrough of Intellicore configured for your practice — your workflows, your questions, no obligation.