Chapter 16: Migration Timeline & Deliverables
Chapter Overview
Target: Complete migration within 2 weeks after Betasky receives a complete, correct migration zip from your agency.
If the zip is missing files, has wrong formats, or fails validation — the clock pauses until you send a fixed package. Archive PDF upload on care orders continues after go-live at your own pace (Chapter 14).
16.1 How delivery works
- Kickoff — Betasky sends folder structure and Chapter 5 checklist
- You export from Axxess (Report Center lists, Profile PDFs, Med Profile PDFs, etc.)
- You pack everything in one zip and send via secure transfer
- Betasky reviews the zip — completeness check before import starts
- 2-week migration window begins when the zip is accepted
- Go-live after your admin completes Chapter 6 verification
One zip, one handoff. Do not send files in scattered emails or partial drops — that delays the timeline.
16.2 Two-week timeline (after zip accepted)
| When | What happens | Who |
|---|---|---|
| Day 1–2 | Zip review + care order working session (if needed) → approved care order CSV | Betasky + your admin |
| Day 2–5 | Validation import (dry run) + summary report | Betasky |
| Day 3–7 | You fix any gaps; re-send zip supplement if needed | Your agency |
| Day 5–10 | Final Production import (setup → staff → patients → care orders → meds) | Betasky |
| Day 10–12 | Your admin runs Chapter 6 verification checklist | Your agency |
| Day 12–14 | Go-live sign-off + staff training / hypercare | Both |
Exact days flex with agency size. ~2 weeks is the goal when the zip is clean.
16.3 When it takes longer than 2 weeks
Timeline extends if:
- Zip is incomplete (missing Patient List, Employee List, Profile PDFs, etc.)
- Zip has wrong files (truncated med PDFs, bad naming, corrupt exports)
- Care order CSV needs another curation round after validation
- Agency is slow to respond to validation report
- Major legacy EMR changes during migration week (cutover freeze broken)
Betasky will tell you exactly what is missing. Send an updated zip (or supplement) and we resume.
16.4 What goes in the migration zip
Pack per Chapter 5 folder structure:
setup/— Employee List, physicians, payers, pharmacies, facilitiespatients/— Patient List, Patient Roster, Profile PDFs, Medication Profile PDFs (active)- Care order source materials for the joint curation session (cert listings, exports, notes)
Not required in the zip: every Schedule Activity PDF for every historical episode. Those upload after care orders exist — your admin in Betasky, phased over time (Chapter 14).
16.5 Deliverable checklist (your side)
- Migration zip sent via secure transfer (encrypted link or Betasky onboarding channel)
- Cutover date and admin contact agreed
- Care order working session completed (for approved CSV)
- Chapter 6 verification signed off before go-live
- Archive PDFs on care orders — ongoing after go-live, not blocking day-one go-live
16.6 Deliverable checklist (Betasky side)
- Zip completeness review within 2 business days of receipt
- Validation report before Production write
- Final import completed within 2-week window (when zip is clean)
- Staff login invites sent
- Go-live support during hypercare period
16.7 After go-live: archive PDFs
Uploading OASIS, visit notes, and POC to historical care orders is not part of the 2-week clock. Your admin attaches PDFs in Betasky whenever ready — weeks or months after go-live is normal.
Next: Chapter 17 — Glossary