Migrate from Eclinicalworks to Weave.
2 documentation-derived translation patterns — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Weave and eClinicalWorks both let patients book appointments online, so a practice on eClinicalWorks can retire Weave Scheduling and move booking onto healow Open Access: patients book from the practice website, the Patient Portal, or the healow app, seeing providers' real schedules and open slots, and Open Access reads and writes against the eClinicalWorks practice schedule so the slot lands directly on the same provider calendar used for documentation, orders, and billing. Keep eClinicalWorks/healow (the system of record — no double-entry or external sync); cut Weave. Open Access runs around the clock (healow cites ~29.5% of self-scheduled visits booked outside business hours), replacing Weave's website 'request appointment' widget without staff approving each request.
- Warning: Weave can run 'with or without an integrated PMS' and posts an appointment request staff approve; Open Access writes directly to the eCW schedule, so rebuild visit-type/provider rules in Open Access before cutting Weave or self-booked visits land on the wrong slot.
- Warning: Weave bundles scheduling with reminders/confirmations and its VoIP phone line — confirm eCW/healow reminders cover the confirmation/reminder cadence Weave sent before turning Weave off.
- Warning: Confirm healow Open Access is licensed and configured (real schedules exposed, slots templated) for the relevant providers before cancelling Weave.
- Warning: If the practice runs Weave because its prior PMS was not integrated, verify eClinicalWorks provider schedules and templates are fully built so Open Access has real bookable slots on day one.
Weave and eClinicalWorks both run two-way patient messaging, so a practice on eClinicalWorks can retire the standalone Weave contract and move the conversation into the eClinicalWorks Patient Portal and healow app: patients send secure messages straight to the clinic, the thread is linked to the patient's record inside eClinicalWorks (eCW states the portal is 'tightly linked to the EMR'), and staff triage messages on their own schedule instead of the phone — covering the scheduling, intake, and billing conversations Weave carried over SMS. Keep eClinicalWorks/healow (the system of record where a reply or refill request becomes part of the chart); cut Weave. Because messaging runs in the same healow stack patients already use for portal and check-in, no separate inbox or paste-back is needed.
- Warning: Weave texts from the practice's own phone/VoIP line and reaches patients who never enroll in a portal; eCW/healow messaging is portal/app-first, so confirm Patient Portal + healow enrollment and keep an SMS notification fallback before cutting Weave or unportaled patients lose the channel.
- Warning: Weave bundles texting with VoIP phone, reminders, reviews, and payments under one login — cutting Weave for messaging alone can strand those adjacent workflows, so scope what else the practice runs on Weave first.
- Warning: Confirm the practice is licensed for the eCW Patient Portal/healow apps and that secure messaging is turned on for the relevant providers before cancelling Weave.
- Warning: Re-point any reminder/confirmation/recall texts Weave automated onto eCW/healow-native outreach so nothing silently stops sending when Weave is turned off.