Why owners go looking
- The cost model. Whatever shape the bill takes, the practice has grown into a different shape than the bill was built for.
- A feature they have seen elsewhere. A demo showed a report, a workflow or a patient app, and the owner wants it. Name the feature and the job it does for you. The job is what you are shopping for, and it may be something you can add on top of what you have.
- A contract they want out of. Whatever the agreement says about term, renewal and notice, read it before you do anything else and confirm with counsel what it says about notice, data export and what you may take with you.
Five questions to answer before you switch
- What moves. List every kind of data in Moxie: the calendar, the patient record, the charts, the online store and the memberships. For each, write export, re-enter or leave behind under a read-only login.
- What breaks. Every link on your site and your Google profile that points at the store or the booking page, every form, every integration, and every habit at the front desk.
- Who re-enters the record. Charts and consents rarely import cleanly. Name the person who will re-attach what the import misses, and count their hours.
- How long the double-entry month lasts. Providers chart in both systems until the last patient on the old calendar has been seen. Put a date on the end of it.
- What the record must keep. Retention rules apply to the old record after the switch; confirm with counsel and your medical director what must be kept, where and for how long.
Reason by reason: what a switch costs and what you can add instead
| Reason you are looking | What a switch costs | What you can add instead without switching |
|---|---|---|
| The cost model | The migration hours, the overlap period paid twice, and a new bill that grows the same way at the next size | A revenue system that fills the calendar the platform already keeps: more bookings against the same bill |
| A report you saw in a demo | A new system learned by every provider for one report | A dashboard built on the Moxie data you already have: calls, bookings, no-shows, reactivations, revenue by provider |
| A reactivation or reminder feature | The chart moved for a job that lives outside the chart | Comeback timing read from the Moxie visit history, sent in the provider's voice, with the reply worked and nothing written into a chart |
| A patient app or online store | The store links replaced everywhere and the memberships re-enrolled | The existing online store linked from the voice agent, the texts and the party invite, so more patients reach it |
| A contract you want out of | Notice, a possible final term and the export, then everything above; confirm the terms with counsel | A fixed exit date on the calendar and a system built on the record, so the exit, if it comes, moves one thing at a time |
When switching is the right call
Sometimes it is. The honest cases: the practice has changed shape, from one provider to several locations or from a med spa to a surgical practice. The record system was chosen for the old shape. Or the clinical team has a documented problem the vendor has not resolved, and the medical director wants it fixed. Or the agreement is ending anyway and the team has already learned another system elsewhere. In those cases, switch, and plan the overlap period on paper before you sign. What is never the right reason: a feature you can add on top of the record you already have.
What NorthCore does either way
NorthCore builds on whatever you keep. If you stay on Moxie, the growth system reads the visit history, answers the phone and the DMs on your number, and books into the Moxie calendar. It times the comeback and puts the numbers on one page. We run on it today in a working practice. If you switch, the same system is built on the new record once the overlap period ends. Either way, nothing is written into a chart and the record stays yours. The page for Moxie shows what stays in it and what the connection is.
How to decide this on Monday
- Write the reason in one sentence. If it names a feature, write the job the feature does.
- Read the agreement, note the notice window and the export terms, and send both to counsel.
- Export one week of data from Moxie and open it. What came out clean, what came out as a file nobody can read, and what stayed behind is your migration plan in miniature.
- Price the overlap period in hours: every provider, the front desk, and you.
- Ask whether the job in step one can be done on top of the record. If it can, that is the cheaper path.
What to do next
NorthCore's Bring patients back solution builds the comeback calendar on whatever record you keep: the list of who is due, the message in the provider's voice, the reply worked until it books. Scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.
