A SaaS company offering back-up cloud solutions approached me to help them writing a blog article. It ought to explain e-mail migrations in simple words. The article explained the context and then guided the user through the process itself. It answered such questions as:
- why migrate from one service to the other?
- what advantages does it have?
- what kinds of migration exists?
- how to plan the migration properly?
This article required extensive research as well as setting up two trial accounts and conducting a test migration to make the screenshots and describe the process properly.
In the end, I come up with an article that summarizes the advantages of the target platform against the legacy, highlights the differences between three kinds of migration — stages, cutover, and hybrid — and outlines a step-by-step migration plan. The article also touched such important issues as internal communication, such as finding tech evangelists and early adopters.
The main part described the migration itself. It explained how to create an integration account, user accounts, transfer the data between two systems, and migrate the data in batches.
The articled concluded with a necessity to back-up both e-mail boxes to prevent losing important data during migration.
The customer later gave me a similar assignment: a blog article that described steps and things to keep in mind for reverse migration.
The main challenge of both articles lay in translating the Microsoft documentation into a blog format. It is always fascinating to decide on what you pick up from the documentation (and what can be dropped) and how you paraphrase it or make it more relevant for your use case.