This blog is the second of a series about content migrations to Microsoft 365
Being able to work and collaborate in a safe manner on a secure device. A promise made by Microsoft 365 and a huge prerequisite to deliver this promiss. To realize this promise your employees need to be able to collaborate on all that content on those dreaded fileshares. An accumulation of company data that has grown over the years, which nobody bothered to clean or restructure. …and now it’s up to you to move it to the cloud. In other words: a content migration.
Personally, I really like migration projects, although I must admit, somewhere along the line of each content migration project I almost always get to a point where I want to bail out.
Content migrations have a tendency to be look at as ‘something that we need to do between the soup and the potatoes – as we say in The Netherlands’ :-). I want to explain that content migrations are much more than a gigantic copy-paste action, but can actually transform your business, they are a starter, an enabler for improving the way you run your business. If your content migration is a success: your transformation will get a huge boost!
I am going to write a series of blog that will guide you transform your business by performing a content migration Microsoft 365-style! The blogs will more or less follow the framework below.
The individual blogs will explain the process of a content migration, what are the pitfalls, what it is you need to accomplish in every process step, when it is time to bail out 🙂 and also how you can streamline, and even, automate the actual migration.
That being said. We will look at a content migration from various perspectives. We will look at it from:
- a business perspective – why do we want to do this? What are the business drivers?
- a project perspective – how are we going to do this and why a content migration is a (serious) project
- a technical perspective – how are we actually going to copy these files? Is there a way to automate this process?
To make it perfectly clear: we are not discussing moving 100 documents to Microsoft 365, we are talking Tb’s of data, hundreds of thousands or even millions of documents.
The plan is to write small, comprehensible blogs:
- Migrate content to Microsoft 365 – Acknowledgement of change
- This blog is about why a content migration to Microsoft 365 will transform your business and why it is not a copy-paste action
- Migrate content to Microsoft 365 – Understand the motivation
- This blog is about that it is crucial, what the business motivation is. This is necessary for your design. This is about the Motivation layer in ArchiMate
- Migrate content to Microsoft 365 – Designing the future
- This blog is about your design for the stakeholders. This is about the business layer in ArchiMate
- Migrate content to Microsoft 365 – Plan your migration
- This blog is about identifying the activities necessary and working accordingly
- Migrate content to Microsoft 365 – Automating your migration using ShareGate
- This blog is about how to use PowerShell to automate your migration
- Migrate content to Microsoft 365 – Automated analysis
- This blog is about how to use Microsoft SQL Server and SSIS to automate your results