Betasky Migration Documentation

Target: within 2 weeks after Betasky accepts your complete migration zip. If the zip is missing files or has errors, the timeline pauses until you send a corrected package. Uploading archive PDFs to old care orders continues after go-live at your own pace.

One secure zip with Report Center exports: Patient List, Patient Roster, Employee List, physicians/payers/pharmacies, Profile PDFs, Medication Profile PDFs for active patients, and materials for the care order working session. Do not scatter files across emails.

No. Visit and OASIS PDFs are archived on migration care orders. When your admin uploads a PDF, Betasky stores it and can register an archive visit on the episode timeline. We do not bulk-import chaotic Axxess Schedule Activity as editable live visits — history is preserved as documents plus archive visits.

No. Export the Axxess Employee List from Report Center — it already includes each person’s Role column (permissions), Title, Credentials, and email. Betasky maps those to Betasky roles during import. You spot-check logins and permissions after import.

You and Betasky build an approved care order CSV with every certification period per patient (Active, Expired, Discharged). Betasky imports all rows as migration care orders. Your admin uploads OASIS, POC, and visit note PDFs to each care order in the dashboard afterward — not all at once during migration week.

Your agency admin uploads in Betasky Care Order Details — anytime after care orders exist. Priority: go-live patients first, then recently discharged, then older retention window. Betasky does not bulk-upload every nursing note for you during the 2-week migration window.

Yes. Axxess is PDF- and Report Center–centric. Clinical history comes from Patient Chart → Schedule Activity prints, not one clean export. Expect a joint care order session and curation — that is normal for Axxess, not a sign something went wrong.