Alfresco to SharePoint Online Migration
Content model mapping + records management + workflow rebuild — refined across 6,500+ SharePoint implementations.
Frequently Asked Questions
Why migrate from Alfresco to SharePoint Online?
Four common drivers. (1) Total cost of ownership — Alfresco Community is free but enterprise support (Alfresco Enterprise / Content Services) runs $50-$150 per user per year plus infrastructure; SharePoint Online is bundled into M365 E3/E5 at effectively no additional cost. (2) Microsoft 365 Copilot integration — Copilot indexes SharePoint natively, does not index Alfresco. (3) Rapid Alfresco skills scarcity — the Alfresco specialist pool has shrunk since Hyland acquired the company in 2020. (4) Consolidation to one collaboration platform — organizations running both Alfresco (records) and SharePoint (collaboration) benefit from unifying.
How does the Alfresco content model map to SharePoint?
Three-tier mapping. (1) Alfresco Types → SharePoint Content Types (native mapping, though Alfresco types are often more granular). (2) Alfresco Aspects (mix-in behavioral traits) → SharePoint Content Type inheritance + sensitivity/retention labels. (3) Alfresco Categories (hierarchical taxonomies) → SharePoint Managed Metadata term sets. Custom Alfresco aspects that don't have SharePoint equivalents (rare) require decision: replicate as content type inheritance, or replace with Purview sensitivity label logic.
How do we handle Alfresco records management?
SharePoint Online Records Management + Purview Retention. Every Alfresco RM classification becomes a SharePoint retention label; the retention rules migrate as Purview retention policies applied to the label. WORM (write-once-read-many) compliance for regulatory records (SEC 17a-4, DoD 5015.2, MoReq) is satisfied by Purview retention labels marked as Regulatory Records. Third-party attestation (Cohasset Associates for SEC 17a-4) available.
What happens to Alfresco workflows?
None migrate as-is. Alfresco workflows are built on Activiti (BPMN engine) with Alfresco-specific extensions; SharePoint Online workflows use Power Automate. Every Alfresco workflow surfaces a triage decision: (a) Archive — workflow no longer used, no migration needed. (b) Replace with simpler pattern — native SharePoint approval, Microsoft Lists automation. (c) Rebuild in Power Automate — for business-critical workflows. See /answers/power-automate-rebuild-after-sp2013-workflow-retirement for the general Power Automate rebuild playbook — same discipline applies here.
What is the typical migration timeline?
Depends on scale + custom content model complexity. Small (under 500 GB, minimal custom model): 3-4 months. Mid-market (500 GB - 5 TB, moderate customization): 6-9 months. Large enterprise (5 TB+, deep custom model + custom workflows): 12-18 months. EPC Group's engagement: Weeks 1-4 discovery + content model mapping design. Weeks 5-10 target-SharePoint governance foundation deploy. Weeks 11-30+ waved content migration with custom mapping + workflow rebuild + user retraining. Refined across 6,500+ SharePoint implementations.
Talk to a senior architect
Email contact@epcgroup.net or call 888-381-9725.
North America's oldest continuous Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.