An EMR data migration checklist should cover seven phases — from pre-migration audit through post-go-live billing validation, to ensure 100% of patient records, active authorizations, future appointments, and outstanding A/R transfer without revenue disruption. Most PT, OT, and SLP clinics delay switching EMRs not because their current system works, but because the migration feels too risky to attempt. The checklist below eliminates that risk. It is built for multi-location outpatient rehab practices managing complex payer mixes, high visit volumes, and teams that cannot afford a single day of billing downtime. Every phase maps to a specific revenue-protection outcome, and the full sequence — from first export audit to first clean claim in the new system — can be completed in as little as one to three weeks for practices under 5,000 patients.

SPRY has completed 100+ clinic migrations with a verified 100% data-integrity match across patients, cases, clinical documents, active authorizations, and future appointments — confirmed by post-go-live audit snapshots showing record-for-record parity between source EMR exports and SPRY imports.

The 72-Hour Revenue Continuity Map™

Most migration guides skip the part that actually keeps clinic owners up at night: what happens to your money during the switch? The 72-Hour Revenue Continuity Map traces the revenue-critical actions across the 72 hours surrounding your cutover — the window where billing disruption either happens or doesn't.

‍

Cutover Window (Friday Evening → Saturday)

‍

What Exactly Transfers During an EMR Data Migration — and What Doesn't

The single biggest misconception driving migration fear is the belief that switching means losing years of clinical history. It doesn't. But knowing exactly what moves and what stays behind is the difference between a controlled cutover and a chaotic one.

What migrates into the new system: patient demographics and contact information (with legacy patient IDs retained for traceability), cases with ICD-10 codes, referring physician and PCP data, visit counts, injury and episode dates, clinical documents including evaluations, daily notes, progress notes, and discharge summaries (converted to searchable PDFs with original signatures and timestamps preserved), future appointments rebuilt by provider, location, and room, insurance records and active authorizations with remaining visit counts and mapped clearinghouse payer IDs, documents and images such as intake packets, referrals, scans, and patient photos, and outstanding patient A/R balances and payment plans.

What remains in the legacy EMR (read-only access): historical claim and EOB line-items (the audit trail stays intact for compliance), obsolete or duplicate payer rows (deduped during migration, not reimported), unfinished notes (clinic completes them pre-switch or opts for post-switch re-import), and past canceled or no-show appointment slots.

The key principle: everything revenue-active and clinically current migrates. Everything archival stays accessible in read-only mode. No data is deleted from either system during a properly executed migration.

The 7-Phase EMR Data Migration Checklist

Phase 1: Pre-Migration Audit (Week 1)

• Inventory all active patients, cases, and authorizations in your current EMR
• Identify duplicate patient records, inactive payers, and orphaned cases for cleanup
• Document your current payer mix and clearinghouse routing (which clearinghouse, which payer IDs, which ERA enrollments)
• Map staff roles and daily workflows — who touches what, when, and why
• Confirm your new vendor's HIPAA compliance, SOC 2 certification, and BAA execution
• Set your target go-live date during your lowest-volume window (Friday evening cutovers protect Monday revenue)

Phase 2: Data Export and Cleanup (Week 1–2)

• Export patient demographics, case records, clinical documents, insurance data, authorizations, and A/R from your current EMR
• Run a deduplication pass — merge duplicate patient records, remove obsolete payer rows, and standardize field formats
• Fix bad or missing payer IDs before import (this is the number one cause of post-migration claim rejections)
• Verify that clinical document exports include signatures, timestamps, and structured data fields — not just flat text
• Reconcile export record counts against your current EMR's database totals

Phase 3: Field Mapping and Configuration (Week 2)

• Map source EMR field names to the new system's standard schema (demographics, case fields, authorization structures, billing codes)
• Configure payer-specific billing rules, authorization requirements, and eligibility check settings in the new system
• Rebuild scheduling templates by provider, location, and room
• Set up clearinghouse EDI connections and test claim submission routing
• Initiate ERA enrollment with each active payer (allow 2–4 weeks for payer processing — start this early)

Phase 4: Sandbox Validation (1–2 Days)

• Import a representative sample of patients, cases, appointments, and billing data into a sandbox environment
• Have clinicians review sample patient charts: are demographics correct, are clinical documents readable, are authorization visit counts accurate?
• Have billing staff verify sample claims: do payer IDs route correctly, do CPT/ICD-10 codes populate, do clearinghouse connections transmit?
• Have front desk staff test patient check-in, copay lookup, and appointment scheduling
• Document and resolve every discrepancy before proceeding to full import

Phase 5: Full Import and Cutover (1–2 Days)

• Submit all pending claims in the legacy EMR — clear the queue before switching
• Run final bulk eligibility verification on the next week's scheduled patients in the new system
• Execute full data import
• Set the legacy EMR to read-only
• Run the record-count audit: export totals versus import totals, category by category (patients, cases, clinical documents, authorizations, future appointments, A/R balances)
• Conduct the 30-minute staff go-live huddle — walk through the morning workflow in the new system

Phase 6: First Billing Cycle Validation (Week 1 Post-Go-Live)

• Monitor first-day and first-week clean-claim acceptance rates (target: 95%+ from Day 1)
• Verify that ERA postings flow automatically and payment reconciliation works
• Confirm copay collection at check-in and kiosk functionality
• Track and resolve any payer-routing rejections or field-mapping errors immediately
• Wrap open legacy claims in the old EMR with coaching from your new vendor's billing support team

Phase 7: Post-Migration Audit and Optimization (Week 2–4)

• Run the formal post-go-live audit report: record counts, field integrity, and any gaps requiring re-import
• Close the migration checklist — every line item signed off by the responsible owner
• Identify workflow optimizations now that the new system is live (documentation speed, scheduling automation, eligibility verification cadence)
• Set 30-, 60-, and 90-day KPI benchmarks: clean-claim rate, days in A/R, denial rate, documentation completion time, schedule utilization

Migration Benchmarks: What "Normal" Looks Like in 2026

‍

Clinics that hit the "top-performing" column almost always share three things: they cleaned their data before import, they enrolled clearinghouses and ERAs weeks before cutover, and they ran sandbox validation with real staff before going live. The checklist above forces all three.

How Migration Support Differs Across Rehab EMR Platforms

‍

SPRY's migration methodology is purpose-built for outpatient rehab. It assumes a payer mix heavy on commercial insurance and Medicare, documentation workflows specific to PT, OT, and SLP, and billing teams that cannot absorb even a single day without claim submission. The platform currently serves 500+ clinics across 35+ US states and holds a 4.8/5 on Capterra (53 reviews), 4.6/5 on G2 (76 reviews), and 4.8/5 on Software Finder (42 reviews).

The Real Risk Isn't Switching — It's Staying

The fear that keeps clinics on underperforming EMRs is almost always about data loss and billing disruption. But the math runs the other direction. Every month on a system that produces a 10% denial rate instead of 2% costs a provider seeing $300K in annual collections roughly $2,000 in reworked or written-off claims. Every month without AI-assisted documentation costs 40+ hours of clinician time spent writing notes instead of treating patients. Every month without automated eligibility verification lets preventable claim denials accumulate.

A structured migration checklist does not just reduce risk. It makes the cost of staying visible — and the cost of switching predictable.

Frequently Asked Questions:

How long does an EMR data migration take for a PT clinic?

Timeline depends on patient volume. Clinics with under 1,000 patients can complete a full migration in as little as one day. Mid-size practices (1,000–5,000 patients) typically finish in two to three weeks including sandbox validation and staff training. Enterprise practices with 10,000–40,000 patients should plan for two to three weeks with parallel workflows and phased location rollouts.

Will I lose patient records during migration?

Not with a properly executed migration. The critical safeguard is the record-count audit — a category-by-category comparison of export totals from the source EMR against import totals in the new system. SPRY's verified audit snapshots show 100% record-for-record parity across patients, cases, clinical documents, active authorizations, and future appointments.

What happens to open claims in my old EMR?

Open claims should be submitted and cleared in the legacy system before cutover. The legacy EMR is set to read-only after the switch, and billing teams can continue to monitor and close outstanding claims there while new claims flow through the new system from Day 1.

How do I avoid billing disruption during the switch?

Three actions matter most. First, enroll your clearinghouse EDI and ERA connections in the new system two to four weeks before cutover so they are active on Day 1. Second, run bulk eligibility verification on the first post-go-live week's patients before the switch. Third, schedule the cutover during your lowest-volume window — a Friday evening switch means you are live Monday morning with no clinic closure.

Do I need to retrain my entire staff?

Not with a modern platform. Sandbox validation lets staff interact with their own patient data in the new system before go-live. A 30-minute go-live huddle on cutover morning covers the Monday workflow. Most staff are charting independently by Day 2 or 3. The key is that the new system is intuitive enough that training is measured in minutes, not weeks.

What if my current EMR vendor makes data export difficult?

Most EMR contracts include data portability provisions, and regulations like the 21st Century Cures Act prohibit information blocking. If your vendor restricts export formats or charges excessive extraction fees, document the request in writing. A migration partner experienced in your source EMR (SPRY has migrated 100+ clinics from WebPT alone) can advise on the fastest extraction path for your specific platform.

‍