Product Requirements Document

ChiroSwitch Migration Studio

A guided, mostly self-serve migration experience that helps clinics switch from ChiroTouch to ChiroHD with dramatically less risk, time, and human onboarding effort.

Overview

Why now: ChiroHD is winning because it's modern and usable, but onboarding and migration are still human-heavy and script-driven, which leadership views as unsustainable at scale. Clinics expect migration of patients, appointments, and clinical history—today this work requires manual scripts and human intervention.

Opportunity: Make "switching" a product capability (not a service), turning the hardest objection into a differentiator.

Objectives

1

Win more deals

Win more head-to-head deals vs ChiroTouch by de-risking switching (time, data fidelity, operational downtime).

2

Scale onboarding

Productize what is currently custom, manual, and specialist-driven.

3

Go-live in days

Enable "go-live in days, not weeks" migration for core data domains.

User Personas

Office Manager / Billing Lead

Primary

Continuity of schedules, payer data, balances, and confidence that nothing "breaks" after the cutover.

Clinic Owner / Lead Provider

Primary

Minimal downtime, preserved clinical history, and a clear plan to protect revenue.

Onboarding Specialist

Internal

Predictable, repeatable workflows that reduce bespoke effort per clinic.

Data Migration Operator

Internal

Observability, idempotency, and tools for edge cases without writing new scripts per clinic.

Functional Requirements

1

Source-system selection + migration plan

User selects source system (MVP: ChiroTouch). Wizard generates a clinic-specific migration plan: required exports, data domains included, and cutover checklist.

2

Secure export intake

Support upload via drag-and-drop files (CSV/TSV/XLSX, ZIP of PDFs) or secure, expiring upload links. Validate file types, virus-scan attachments, surface expected vs provided exports with completeness score.

3

Prebuilt ChiroTouch mapping templates

Known-format mappings for common ChiroTouch exports: Patients/Demographics, Appointments, Insurance/Payers, Balances/Open AR, Clinical history (visit-note PDFs as attachments).

4

Field mapping + transformation UI

Map columns → ChiroHD fields with auto-detected types, transform rules (normalize phone numbers, names, state abbreviations), lookup mapping tables. Save mappings as reusable templates.

5

Data quality validation + reconciliation

Deduplication suggestions, pre-import reconciliation report (counts, missing required fields, conflicts), post-import reconciliation with comparisons and exceptions list.

6

Import execution with observability

Asynchronous import jobs with progress by domain, estimated completion time, downloadable error logs and "fix + re-run" flow. Idempotent retries (re-running doesn't duplicate records).

7

Cutover tooling

"Freeze window" guidance: last export time, appointment delta strategy. Optional "delta import" for appointments created since last export.

8

Role-based access + audit

Only authorized roles can upload/export PHI, run imports, or view raw files. Audit logs for all migration actions.

Success Metrics

Conversion / Growth

  • +X% win rate vs ChiroTouch in competitive deals
  • % of new signups originating from ChiroTouch

Onboarding Efficiency

  • Median onboarding specialist hours per clinic reduced by ≥50%
  • Median time from contract → first day live reduced by ≥30%

Migration Quality

  • ≥95% migrations complete without engineering intervention
  • <2% of migrated patients require manual correction post-go-live

Customer Outcomes

  • NPS for onboarding/migration improves (target segment: clinics switching from incumbents)

Rollout Plan (≤6 months)

Weeks 1–4

Discovery + Design

Validate top 10 data domains requested in migrations. Define v1 scope and "minimum acceptable migration" contract.

Weeks 5–10

Build v1

Upload + mapping + validation + import jobs + reconciliation.

Weeks 11–14

Internal Dogfood

Run 3–5 historical migrations end-to-end; harden logs, retries, and templates.

Weeks 15–20

Pilot

3 clinics switching from ChiroTouch (size mix: solo, 3-provider, multi-location).

Weeks 21–24

GA

Launch playbook + enable Sales/CS + publish migration guarantees and scope.

Go-to-Market Strategy

"Switch from ChiroTouch in a weekend."

  • Sales enablement: Standardized migration scope + "data fidelity" checklist. Demo mode showing migration dashboard, reconciliation report, and audit trail.
  • Growth: Limited-time offer "free migration" using ChiroSwitch (reduces perceived risk while testing scalability).

See the companion PRD: Intake-to-Exam Smart Notes

Learn how these features fit into the AI-Forward PM Practice or read the competitive analysis.