Switching platforms mid-year is routine for growing medspas, but good faith exam (GFE) records are the one dataset you cannot afford to lose, corrupt, or leave unverifiable during the move. Here is the exact sequence that keeps every exam legally defensible before, during, and after a software cutover in 2026.
- Transition good faith exam records with a 4-step sequence: export, parallel-run, verify, then sign-off before retiring the old system.
- Run a 60-90 day parallel documentation window so no exam exists in only one system at a time.
- Get your collaborating physician or medical director to co-sign the migration audit trail, not just the new platform.
- Most compliance gaps happen when practices delete the old system before state retention periods lapse.
- A software switch is the right moment to confirm good faith exam requirements haven’t shifted in 2026.
Why this matters
A good faith exam is the legal record that a licensed provider evaluated a patient before an aesthetic treatment plan started. If that record can't be produced during a state board inquiry because it's stuck in a decommissioned system or missing a signature field the new software doesn't support, the exam might as well not exist. Software vendors migrate the easy fields — name, date, treatment code — and drop the harder ones: provider attestation timestamps, supervising physician sign-off, and the audit trail showing who accessed the chart and when.
Medspas that treat a platform switch as a pure IT project, not a compliance project, are the ones that show up in good faith exam requirements audits with unexplained gaps. The fix isn't complicated, but it has to happen in order.
How do you transition good faith exam records during a software switch
The transition happens in four phases. Skipping the order — especially jumping straight to importing everything and deleting the old system — is what creates the gap regulators flag.
- Export every record in its native, unaltered format. Pull PDFs or signed originals, not reformatted summaries the new system generates on import. A reformatted record loses the original timestamp and signature metadata that proves the exam happened when it says it happened.
- Map every required field before you migrate a single chart. Good faith exam templates vary by state, and the new software's default template may not include a field your old one had — supervising physician name, license number, or exam location. Build the field map first, migrate second.
- Run a parallel documentation window of 60-90 days. New exams get logged in both systems during this window so there's never a period where a record exists in only one place with no backup.
- Get written sign-off from your collaborating physician or medical director before you retire the old system. This isn't a courtesy step. It's the person whose license is attached to those records confirming the transferred files are complete and unaltered.
Step 1: Export before you migrate
Don't let the new vendor pull your data through an API without a manual export as backup. Vendor migrations fail silently more often than practices expect — a field that doesn't map cleanly just gets dropped, and nobody notices until an audit six months later. Keep a local, encrypted export of every exam record as of the cutover date. That is your fallback copy if the new system's import corrupts anything.
Step 2: Field-map before you import
A table is the fastest way to see what's missing.
| Field | Old system has it | New system default | Action needed |
|---|---|---|---|
| Exam date and time | Yes | Yes | Verify timestamp format matches |
| Supervising physician name and license | Yes | Sometimes | Add custom field if missing |
| Patient attestation signature | Yes | Yes | Confirm signature image transfers, not just a checkbox |
| Treatment plan notes | Yes | Yes | Spot-check formatting after import |
| Chart review sign-off | Sometimes | Rarely | Almost always needs a custom field |
If your practice already struggles to keep chart reviews documented consistently, this is a good checkpoint to revisit how you document chart reviews for medical director compliance so the new system doesn't inherit an old gap.
Step 3: Run the parallel window
During the 60-90 day overlap, staff log new exams in both platforms. It's more data entry, and your team will push back on it. Hold the line anyway. This window is what lets you prove continuity if a board inquiry lands in the middle of the switch, which is exactly when practices are most exposed.
Step 4: Get physician sign-off before decommissioning
The collaborating physician or medical director attached to your practice should review a sample of migrated records — not all of them, but enough to confirm signatures, timestamps, and field completeness survived the move. Document that review in writing with a date. Only after that sign-off should you cancel the old software subscription or purge its data.
Get physician sign-off on your migration
Medical director and collaborating physician support during a software switch.
Why the transition timeline varies
Not every migration takes the same amount of time or carries the same risk. The variables that change your timeline:
- Number of active good faith exams on file. A solo injector with a few hundred records moves faster than a multi-location group with tens of thousands.
- Whether the old system exports natively or requires manual PDF pulls. Some legacy platforms don't offer bulk export at all, which turns a two-week project into a two-month one.
- State retention requirements. Retention length is set by state rules, and it dictates how long you keep the old system live in read-only mode.
- Whether your collaborating physician arrangement changed at the same time. Combining a software switch with a new physician agreement doubles the documentation load — see how to switch good faith exam providers without gaps in compliance if both are happening at once.
- Number of locations sharing one system. Multi-location groups need a location-by-location cutover schedule, not a single flip-the-switch date.
- Whether the new platform captures provider e-signatures the way your state requires. Not every EHR built for general medical practice accounts for aesthetic-specific good faith exam rules.
Do I need to keep the old software subscription active during the transition?
Yes — keep the old subscription active in read-only mode through the entire parallel documentation window and until your collaborating physician signs off on the migration audit. Canceling early to save on subscription costs is the most common way practices lose access to a record they need later in 2026.
How long should good faith exam records be retained after a software switch?
Retention length is set by your state's medical board rules, not by the software vendor, so confirm the retention period with your collaborating physician or medical director before deleting anything from the old system. Migrating software doesn't reset or shorten that clock.
Who signs off on a good faith exam records migration?
The collaborating physician or medical director attached to the practice should sign off, not an office manager or IT contractor. Their attestation that the migrated records are complete and unaltered is what protects the practice if the migration is ever questioned.
FAQ
What’s the biggest risk when switching medspa software mid-year?
The biggest risk is a window where a good faith exam record exists reliably in neither system during cutover. Running a 60-90 day parallel documentation period closes that gap before it becomes a compliance problem in 2026.
Is it better to migrate all locations at once or one at a time?
One location at a time is safer for multi-site medspas because it limits how many records are exposed if the import fails on the first attempt. A single-location pilot also lets you fix field-mapping issues before scaling.
Can my new software vendor handle the compliance review of migrated records?
No. A software vendor can migrate data but cannot attest that migrated exam records meet your state’s good faith exam requirements. That review belongs to your collaborating physician or medical director.
How much data entry does the parallel documentation window add?
Staff log each new exam in both the old and new system during the overlap, which roughly doubles data entry for that window only. It is temporary, and it is the step that protects the practice if a board inquiry lands mid-migration.
What happens if a good faith exam record is lost during a software switch?
A lost record means the practice cannot prove the exam occurred, which puts the associated treatments at risk during any board review. That is why a manual export and a local backup copy happen before migration starts, not after.
Should I switch collaborating physicians at the same time as switching software?
Avoid combining both changes in the same window when possible, since it doubles the documentation burden during an already sensitive transition. If a physician change is unavoidable, stagger it so the software migration is signed off first.
How much of the migrated record set should be spot-checked?
Review enough records to cover every exam type your practice performs, including the least common ones, since rare templates are where field mapping fails. Pull records from different months rather than one date range.
Does a software switch change my good faith exam obligations?
No. The exam requirement is set by state law and your supervision arrangement, not by the platform you document in. A switch is a good moment to confirm your 2026 obligations haven’t changed independently.
One last thing
The part practices miss most often isn't the data export. It's the signature. Plenty of platforms migrate the checkbox that says signed but drop the actual signature image or the timestamp tied to it, and that distinction is exactly what a board reviewer checks first. Before you decommission anything in 2026, pull five random migrated records and confirm the signature artifact itself transferred, not just a field claiming it did.
If your practice is running this transition without a collaborating physician actively reviewing the migration, that's the gap US Medical Directors closes — medical director oversight, chart review, and good faith exam support that carries through a software change instead of getting lost in it.
Related guides
