Strukton
Migration from OpenText eDOCS to SharePoint Online
The Complexities Of Migrating From OpenText eDOCS To SharePoint Online
- A thorough assessment of Strukton’s source content was required to point to errors, inconsistencies and relationships surrounding content.
- Folders in OpenText eDOCS were not representative due to large volumes of unfiled documents based on metadata associated with different Strukton departments.
- Content in OpenText eDOCS repositories required segregation and migration to consolidated content types and different site collections in SharePoint Online.
- A review of the existing information architecture was needed to determine necessary mapping and transformation rules based on metadata required for migration.
- Related documents stored in Strukton’s OpenText eDOCS platform with similar metadata required migration to the same target location/container within SharePoint
- An audit trail and metadata-based reports were required for the entire migration, to ensure all the items in scope of migration had been moved across correctly.
Discovery & Analysis
Migration Accelerator’s drill-down discovery reports and pre-migration checks identified potential migration issues, helped decide on an efficient migration strategy and established the requirements of a target information structure.
Information Architecture Optimisation
Migration Accelerator’s Metadata-based target structure mapping feature mapped documents to an information architecture which closely matched Strukton’s internal organisational and departmental hierarchy.
Migration Design & Configuration
With the need to extract additional metadata based on the parent folder’s metadata, migration rules were setup via Migration Accelerator to map assets into respective content types. Rules were applied to logically migrate related items.
Pilot Migration
Proventeq carried out an end-to-end pilot migration to closely examine the existing content landscape and to highlight potential issues and complexities which would require attention prior to the production migration process.
Incremental Live Migration
The migration was staged to allowed for departmental availability. Proventeq’s team generated custom reports based to ensure the entire content portfolios of respective departments was migrated successfully.
The Results
Optimised Content Architecture
To allow Strukton to optimise their content architecture in SharePoint, Proventeq ensured that content stored in disparate source systems, including archived data, were consolidated and standardised along with all their metadata.
An item level audit along with metadata ensured that every content was successfully cleansed, transformed and migrated to comply with the constraints of the new environment.
Seamless Transition To SharePoint
The adoption of pilot, live and delta migration processes helped to ensure that Proventeq’s strategy met the needs of the project; staging the migration over period of months helped Strukton to avoid any costly or time-consuming technical issues and ensured that departments across the organization would be able to access content and information as needed both during the project and after the migration’s completion.
Minimal Impact To Business Activities
Automation of complex migration processes, and reuse of the same process for different source systems ensured reduced effort. This minimised the impact on business-critical processes and resulted in a reduction in overall project cost.
With Proventeq advising on best practice for OpenText eDOCS to SharePoint migration, Strukton’s team was assured to continue their business as usual during and after migration.
