So friends in this next post as part of my series which I’m wrapping up, on solution architecture for the Power Platform, I want to talk about considerations for a post go-live topic being data migration!
For new solutions we’re implementing that we may have requirements to migrate data from a legacy system to the new solution we’re implementing. Let’s look at some considerations for that in this post!
Recap on go-live considerations
If you haven’t read the previous post to this within this series, check it out now…
When do we do this?
So friends, here’s the thing. Data migration is another thing that shouldn’t only be done post go-live. This is something we should have tested in a test environment and completed for a UAT environment as users will require data for user acceptance testing. In fact at every stage of the testing process, data will need to be present… especially if we’re migrating from a legacy platform. So embed this into your ALM process!
Get the data
So friends, often the process of getting hold of the data you’ll need will take a while as you’ll need to wait on stakeholders in the customer organisation for this. Plan in plenty of time to allow for this to happen! 🙂
Prioritise migration
So whilst full planning of data migration doesn’t need to be something completed in the initial project plan that can kick off development, it’s for sure something we need to start as soon as development has started and our consultants have work to be doing. This is such an important area people and it absolutely has to be planned into the scope and time we have for a project.
What’s coming up?
So friends in the next couple of posts we’ll continue to talk about data migration focusing next on methods for executing it, and after considerations for testing the output of the process. Stay tuned! 📧