A complete 14-day EMR migration checklist covering data export, import mapping, sandbox testing, staff training, and go-live. Includes what to tell your patients and common mistakes to avoid.
Switching EMRs does not have to be a six-month project. With a structured migration plan, most practices can move from their current system to a new one in 14 days without losing data, disrupting patient care, or overwhelming staff.
This checklist covers every step: what to export from your current system, how data gets mapped and imported, what to test in the sandbox, how to train each role, and how to communicate the change to patients. Use it as a timeline, not just a list.
Before you start: pre-migration preparation
Identify your migration team: You need one person from each role: a practice manager (overall coordination), one practitioner (clinical workflow validation), one front desk staff (scheduling workflow), and one biller (claims workflow). Each person commits 3-5 hours over the 14-day period.
Document your current workflows: Before changing systems, write down how your team currently handles: new patient intake, appointment booking, check-in, charting, coding, claim submission, and payment posting. These become your testing scenarios for the sandbox.
Notify your IT or hosting provider: If your current EMR is server-based, coordinate with your IT team on data export timing. If cloud-based, confirm your export options (CSV, HL7, API).
Days 1 to 3: account setup and configuration
Day 1: Create your organization in the new EMR. Set up departments, specialties, and service locations. Configure operating hours, time zones, and appointment types with correct durations.
Day 2: Create practitioner profiles with NPI numbers, credentials, taxonomy codes, and department/specialty/location assignments. Set up shifts and availability for each practitioner.
Day 3: Configure roles and permissions. Set up user accounts for all staff. Configure billing settings: payer list, fee schedules, place of service codes, and rendering provider defaults.
Days 4 to 7: data import
Day 4: Export data from your current EMR. Most systems support CSV export of: patient demographics, insurance information, appointment history, and clinical notes. Export each category separately.
Day 5: Run the import tool. Map fields from your export files to the new system's fields. The import tool flags: duplicate patients, missing required fields, format mismatches (date formats, phone number formats), and records that need manual review.
Day 6: Review flagged records. Resolve duplicates (merge or keep separate). Fix formatting issues. Verify a random sample of 20 patient records to confirm data accuracy: demographics, insurance, and appointment history should match your old system.
Day 7: Import clinical templates. If your current EMR has custom note templates, recreate them in the new system. Most EMRs provide specialty-specific system templates that cover 80% of use cases. Customize the remaining 20% for your practice's documentation patterns.
Days 8 to 10: sandbox testing
Day 8: Test the scheduling workflow. Book, reschedule, and cancel appointments. Verify status colors, practitioner filtering, and multi-location views work correctly. Test the AI Receptionist: trigger a confirmation SMS and verify it sends correctly.
Day 9: Test the clinical workflow. Open a patient chart, start a visit note, document using your templates, add CPT and ICD-10 codes, and sign the note. If using AI Scribe, test a sample visit to see the drafted note. Verify the note flows to the billing queue after signing.
Day 10: Test the billing workflow. Submit a test claim through the sandbox. Verify eligibility checks run correctly. Test payment posting and patient statement generation. If using the AI Billing Agent, verify code suggestions appear on signed encounters.
Days 11 to 13: staff training
Day 11: Front desk training (2-3 hours). Cover: patient check-in, appointment booking, calendar navigation, insurance verification, and AI Receptionist settings. Focus on the daily workflow, not every feature.
Day 12: Practitioner training (1-2 hours). Cover: opening a patient chart, starting a visit note, using templates, AI Scribe review and signing workflow, lab orders, and e-prescribing. Practitioners need the shortest training because the clinical workflow is the most intuitive part of any EMR.
Day 13: Biller training (2-3 hours). Cover: claims dashboard, claim review and submission, ERA/EOB processing, payment posting, denial management, and AI Billing Agent code suggestions. Billing is the most complex workflow and benefits from the most training time.
Day 14: go-live
Morning: Switch DNS or login credentials to point to the new system. Your onboarding manager is available by phone and screen share for the entire first day.
During the day: Your team uses the new system for all patient interactions. The old system remains accessible (read-only) for reference. Any issues that arise are resolved in real time with your onboarding manager.
End of day: Debrief with your migration team. Identify any workflows that felt different from expected. Schedule a follow-up check-in for Day 21 (one week post-launch).
What to tell your patients
Most patients will not notice the switch. The changes they see are: a new phone number or sender for SMS reminders (if applicable), a new patient portal URL, and potentially a new look to appointment confirmation messages. Send a brief email or text one week before go-live: "We are upgrading our practice management system. You may notice updated appointment reminders starting [date]. No action is needed on your part."
Common migration mistakes to avoid
Mistake 1: Trying to migrate everything at once. Not all historical data needs to move. Focus on: active patients (seen in the last 2 years), current insurance information, and recent clinical notes. Archive older records in your previous system.
Mistake 2: Skipping sandbox testing. Every practice that regrets a migration skipped the testing phase. The sandbox catches formatting issues, missing data, and workflow gaps before they affect real patients.
Mistake 3: Training everyone at once. Role-specific training is more effective than all-hands sessions. Front desk, practitioners, and billers have different workflows and different questions.
Mistake 4: Cutting off the old system too early. Keep your previous EMR accessible (read-only) for at least 30 days after go-live. Staff will occasionally need to reference historical information that did not migrate.
Frequently asked questions
Can I migrate from any EMR to Trustro?
Yes. Trustro's data import tool accepts CSV, Excel, and structured data exports from any EMR. The most common migrations are from Jane.app, SimplePractice, athenahealth, DrChrono, and Tebra. Each has documented export procedures that your onboarding manager will guide you through.
What data can be migrated?
Patient demographics, insurance information, appointment history, clinical notes (as text), lab results, and billing history. Custom templates can be recreated. Scanned documents and images can be imported as attachments.
Is there any downtime during migration?
No. Your current EMR stays fully active during the entire 14-day migration period. You switch to the new system on Day 14. There is no gap in operations or patient care.
What if something goes wrong on go-live day?
Your onboarding manager is available by phone and screen share for the entire first day. Your previous EMR remains accessible as a fallback. In practice, critical issues on go-live day are rare because the sandbox testing phase catches them in advance.
The bottom line
EMR migration is a 14-day project, not a 6-month ordeal. The key is following a structured timeline: setup, import, test, train, launch. Skipping steps (especially sandbox testing) is what makes migrations painful. Following the checklist is what makes them routine.
Ready to start? Book a migration walkthrough at /demo. We will show you the timeline with your specific data volume and team size.
Related reading
Read more: /blog/sandbox-testing-before-emr-go-live
Read more: /blog/real-cost-of-switching-emr
See how this works in the product: /demo