If you run an Allscripts (now Veradigm) EHR and you are moving to a dominant platform, the migration’s difficulty lives in the details — custom forms and templates, custom reports, FollowMyHealth, dbMotion, and a marketplace of third-party integrations. Taction Software runs Allscripts and Veradigm migrations for hospitals and provider groups moving to Epic, Cerner (Oracle Health), athenahealth, MEDITECH Expanse, or a custom-built EHR — handling source-environment extraction, data engineering, and integration cutover with zero data loss and minimal clinical downtime.
This page covers migrating off Allscripts. For other paths or a general overview, see our EHR migration services; if you instead need to integrate with an Allscripts system you are keeping, see our Allscripts integration work.
Schedule an Allscripts Migration Strategy Call → (NDA-protected)
When Allscripts Customers Migrate
Allscripts Sunrise Roadmap & Divestiture Considerations
Allscripts’ acute-care products, including Sunrise, became part of Altera Digital Health after Veradigm divested that business. Some organizations reassess their long-term EHR roadmap in light of that change and the platform’s trajectory.
Veradigm Strategy Shifts
Strategic shifts at Veradigm prompt some customers to re-evaluate whether their current EHR still fits their direction for the next decade.
Health System Consolidation
When health systems consolidate, standardizing onto one dominant EHR is a common driver for migrating Allscripts sites onto the acquiring system’s platform.
Interoperability & FHIR API Requirements
Growing interoperability and FHIR API requirements lead some organizations toward platforms that better fit their long-term integration strategy.
Allscripts Products We Migrate From
We migrate from the full Allscripts / Veradigm line: Allscripts Sunrise (acute care), Allscripts Professional EHR (ambulatory), Allscripts TouchWorks, Allscripts Practice Management, and the FollowMyHealth patient portal.
Target EHRs We Migrate To
We migrate Allscripts environments to Epic, Oracle Health (Cerner), athenahealth, MEDITECH Expanse, or a custom-built EHR for specialty practices — drawing on our Epic EHR integration experience and, for Cerner-bound systems, our dedicated Cerner-to-Epic migration practice.
Allscripts Migration Methodology
Source Environment Discovery
We profile the Allscripts environment — data, custom builds, reports, and interfaces — so scope is understood before design.
Data Mapping & Transformation Engineering
We build and validate the ETL and transformation rules into the target EHR, as part of our custom healthcare software development engineering.
Integration Cutover Planning
We plan and rebuild the interface fabric in the target system using HL7, FHIR, and Mirth Connect.
Phased Go-Live with Rollback Capability
We support a phased go-live with reconciliation reporting and rollback paths at every step.
Specific Challenges of Allscripts Migrations
Data Model Complexity
The real work is in the customizations: custom forms and templates, custom reports, and workflow configurations that have to be understood and either translated or retired deliberately.
Integration Footprint
Allscripts environments carry a distinctive integration footprint — FollowMyHealth, Allscripts Open API and dbMotion, and third-party Allscripts Marketplace integrations — each of which needs a deliberate plan in the target system.
Timeline & Investment
Typical Range: 9–18 Months
Most Allscripts migrations run nine to eighteen months, depending on which products are in use, environment size, and customization volume.
Cost Drivers Specific to Allscripts Migrations
Cost is driven largely by the volume of custom forms, templates, and reports, the dbMotion and FollowMyHealth footprint, and the number of marketplace and third-party integrations to rebuild. We give a firm, scoped estimate after the strategy call.
Schedule an Allscripts Migration Strategy Call →
Frequently Asked Questions
How long does Allscripts migration take?
Typically nine to eighteen months, depending on the Allscripts products in use, environment size, customization volume, and integration footprint. We provide a firm timeline after the strategy call.
What about custom Allscripts builds and templates?
Custom forms, templates, reports, and workflow configurations are the main source of migration risk. We catalog them in discovery, translate the ones you still need into the target EHR’s equivalents, and retire the rest deliberately.
Can we keep FollowMyHealth during transition?
We plan the patient-portal transition explicitly — including how long FollowMyHealth remains in place and how the move to the target system’s portal is sequenced — so patients are not left without access during cutover.
How do you handle the dbMotion integration footprint?
We inventory the dbMotion and Allscripts Open API footprint in discovery and rebuild the necessary data flows in the target environment, so interoperability continues after the source system is retired.
Schedule an Allscripts Migration Strategy Call →
Reviewed by Taction Software’s EHR migration and healthcare integration engineering team. ISO 27001-certified information security management. PHI is handled under a signed BAA with safeguards preserved throughout — see our healthcare data security practice.