Migrating from a legacy practice-management system
The data-mapping playbook for clinics moving to Faurenis from an existing PMS.
AdminPractice managerIT / Security· 11 min · Updated 2 May 2026
Summary
Migration is the single largest source of friction. This guide describes the staged approach Faurenis uses to move clinics over: parallel run, validation, cutover, and reconciliation.
Checklist
- Inventory your existing patient population.
- Export the legacy data in CSV or FHIR.
- Confirm the field map with the Faurenis migration engineer.
- Run a two-week parallel cycle with the legacy system in read-only.
- Reconcile any patient who exists in only one of the two systems.
- Cut over scheduling on a Monday; keep the legacy export for 90 days.
Field mapping
The most common mapping issue is between legacy "treatment codes" and Faurenis "procedures". The Faurenis migration engineer maps these in a spreadsheet you approve.
Parallel run
For two weeks, all visits are double-recorded. The clinician notes go into Faurenis; the legacy PMS keeps its existing data flow. At day 14 you decide whether to cut over.
Cutover and reconciliation
Cut over on a quiet Monday. Reconcile any patient with discrepancies in the following week. Keep the legacy export for 90 days for audit.