Migrating to Medplum

Consider the following common scenario:

• You have an existing digital healthcare platform running active operations
• You decided to adopt a standards based architecture, such as Medplum
• You want to migrate operations without service interruption or degradation

Migrating non-FHIR data into Medplum requires engineering work, but the hardest problems are usually decisions about meaning, ownership, and cutover rather than converting file formats. We have seen migrations go most smoothly when teams make those decisions explicitly and test them against representative data. This series of guides walks through that process.

Planning this migration?

The Data Migration Decision Guide can help you inventory sources, define ownership, choose a cutover strategy, and agree on acceptance criteria.

The implementation guides cover:

1. Plan your migration
2. Sequence your migration
3. Govern data mappings
4. Convert your data to FHIR
5. Build data pipelines
6. Validate and reconcile migrated data
7. Test and accept migrated data
8. Adopt Medplum and retire the legacy system

Start with Planning your migration after the discovery decisions and success criteria are documented.