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 optionally care-orders.csv (one row per cert period — see migration guide). 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 build a care order CSV with every certification period per patient. For in-care patients: older certs Expired, current cert Active, future certs Pending Assessment. For discharged patients: earlier certs Expired, final cert Discharged. Betasky imports all rows; your admin uploads PDFs afterward.

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. Care order status in Axxess is often wrong — you curate cert periods in care-orders.csv using your cutover date. An optional Betasky review call can spot-check that file before import.