HIPAA-Compliant Notion to SharePoint Migration — How Emergicon Moved 31K+ Blocks with Zero Downtime

TL;DR

Customer: Emergicon (EMS and fire department billing specialists)

The Move: Notion to SharePoint

The Scope: 400+ databases (as SharePoint lists), 9,600+ list rows, 32,000+ content blocks, 1,800+ comments, 45+ standalone pages, and 15+ SharePoint sites.

The Roadblock: HIPAA-compliant documentation at high stakes, plus the risk that a DIY or scripted move could destroy data.

The Outcome: Group-based permissions in SharePoint, zero operational downtime, and full data retention—with users barely noticing the cutover.

By the Numbers

• Content blocks migrated: 32,000+
• Databases migrated (as SharePoint lists): 400+
• Database items (as list rows): 9,600+
• Comments preserved: 1,800+
• Standalone pages: 45+
• SharePoint sites created: 15+
• Notion team spaces mapped for permissions: 13

The Challenge: Data Safety and Strict HIPAA Compliance

Emergicon handles sensitive Emergency Medical Services (EMS) and fire department billing. Their infrastructure requires strict HIPAA compliance and absolute data security. While their team of about 40 users had successfully adopted Notion for integrated documentation and AI workflows, the organization faced a familiar problem: cost redundancy.

Because Emergicon was already paying for Microsoft 365 and had substantial capacity in SharePoint, leadership chose to migrate from Notion to SharePoint. The IT team quickly concluded that a DIY move was not viable.

The ClonePartner Solution: Delta Passes and 1-to-1 Permission Mapping

Emergicon needed a partner that specialized in the Notion-to-SharePoint pathway. After searching, they found ClonePartner could map their complex team spaces and execute the migration without the all-or-nothing risk of a manual export.

The process included:

• Delta migration passes: To limit downtime, the team used a stair-step approach. Users moved to read-only access while ClonePartner ran multiple delta copies to capture changes during the move.
• Complex table handling: The migration involved hundreds of databases. Where a team needed a highly customized dynamic table, ClonePartner iterated until the data behaved correctly in SharePoint.
• Fluid engineering support: For edge cases, engineering stayed in the loop on format options and feasibility—not a one-size-fits-all import.

Ensuring HIPAA Compliance: Security and Permission Mapping

Because Emergicon handles private EMS documentation, security was non-negotiable. The migration could not weaken HIPAA posture or expose sensitive data across internal departments.

ClonePartner translated Emergicon’s existing access model: member lists and access levels from 13 distinct Notion team spaces were mapped to Microsoft 365 Groups, so when users opened SharePoint, read/write access matched the prior environment. That kept a locked-down posture from day one without forcing the IT team to rebuild permissions by hand.

The Results: "Haven't Heard a Peep"

The transition was smooth enough that internal IT had to remind people the migration was underway—there was little interruption to day-to-day work.

Months after cutover, tens of thousands of content blocks and nearly 10,000 database items remained accessible and secure.

Advice for IT Leaders

David and Andy’s recommendations for teams facing a high-volume migration on a deadline:

• Don't bet the farm on DIY: API depth and migration-specific experience matter when a bad script can destroy production data.
• Coordinate user access: Use a read-only phase so final delta syncs are not fighting live edits.
• Align permissions early: Map legacy team spaces to target security groups (for example Microsoft 365 Groups) so the new environment stays locked down from launch.