M365 CAB

Us in the R/IM team (local government) have no IG capability in our M365 ecosystem; we know teams use it as their repository but we're not 100% across the scope. This terrifies us, don't worry. We have an EDRMS but it's not intuitive for our user base, so they're not using it, and we're considering a migration to M365 as our R/IM repository.

We're at the exploratory stage, and working on a business case for executive endorsement, and as part of this we'd love to know what key factors we need to consider as part of a migration exercise - costing, resourcing, specs & config, responsibilities, etc.

Can anyone help with an answer? 

Comments in the chat include:

• When migrating EDRMS data to SharePoint (or indeed, between any systems), consider how the migrated data will appear in the new system; and whether you will bring across everything. e.g. EDRMS systems are usually configured with a range of object types, metadata, etc. which make sense in a RM world. However, SharePoint is usually the meeting place for a greater range of information types and business processes. Therefore, you may need to consider simplifying your architecture rather than trying to create a detailed information architecture for every business process.