Royal Ahrend
Migration from IBM Filenet to SharePoint Online
Royal Ahrend's Unique Challenges
Bad user experience
User Interfaces (UI) in the legacy ECM are unfriendly and challenging to work with, which created a bad user experience and had a negative impact on efficiency and productivity.
Complex to manage and maintain
Content was stored according to the file types available in the legacy FileNet system. The poor information architecture made it hard to manage and maintain.
Inefficient and high management costs
The metadata in the legacy FileNet platform was either missing or incomplete and needed adding from various sources . This was time consuming and costly to manage.
Compliance and security Issues
Dossier documents were filed in common object stores in FileNet instead of customer-specific locations which created compliance and security issues.
The solution
Discovery & analysis
We used our Content Analyser to understand and identify the existing content landscape in FileNet. We also ran a pilot migration to prove that the revised content architecture worked as per business expectations prior to commencing the full migration.
IA optimization
Using custom classification rules, we consolidated multiple content types from 29 down to 5 in the target SharePoint system, thereby creating a simplified structure.
Security & compliance
During the migration, we enriched and restructured Royal Ahrend’s content via classification, security remapping, metadata and taxonomy. We also moved dossier documents from the common object store to customer specific document libraries to ensure security and compliance.
Full-Fidelity migration
Once the IT team at Royal Ahrend were satisfied with the migration design and target system architecture, Migration Accelerator was utilised to execute a full-fidelity migration with an item-level audit trail. This ensured that all items were successfully migrated.
