Discussion in the last Blog Post was all about "Analysis" and in this post I wanted to move onto what I call the next step.
"Rationalization" or if you want to take a less technical and esotertic approach the "Rules by which we will plan and run our migration"
This is one of those phases in a migration where the better understanding of the organization rules, roles and compliance will keep you on track.
I like to think that a successful migration is when you move the pertinent data in a timely manner with no loss or requests for more data.
A lot of folks will just take the approach that if I move everything then I don't risk an issue. This would be akin to always moving to a bigger house
because you were afraid to get rid of anything. Unfortunately for many of us we have seen this in our environments, my experience is that this is
called Exchange Public Folders. Not to mention many of you have retention and compliance guidelines that this type of migration would violate.
So what are these rules and where do they come from?
From the initial "Analysis" phase of the project you should have a good understanding of both the Source and Target environments.
This understanding will lead you to the Questions and Decisions that make up a successful "Rationalization" phase of your project.
While this is not a complete list of questions for the "Rationalization" phase of the project you should be getting the point.
Each of the answers to questions like these is going to affect not only how much data you are required to migrate, but how
much of the data and layout can be left behind. Also note that this is not only about data but timelines for migration as well,
which can and will affect how you plan and migrate your data.
In the next entry I will be discussing putting together the "Analysis" and "Rationalization" phases to drive your "Discovery"