I’d add seperate the human (emotional) aspect from the facts. People have the right to be anxious about delays, it shows their commitment to the work provided (would be worse to get no emotions when issues are raised) Next, focus on issue resolution by taking things step by step. Important not to take all at once, as this might result in more failures. Go step by step, communicate very detailed and make sure all stakeholders are onboard. Identifying the root cause of the issues often provides 60% of the solution.

First action "Don't Panic". Doing a quick impact assessment with a plan for temporary workarounds (if any) and way to resolution is key for such issues. Building confidence with stakeholders that you completely understand the issues and impact of same and you have it under control for resolution helps to calm the stakeholders and get their confidence. if required you can assist stakeholders to out a response for their data consumers

Understand what is wrong and caused to flag data migration procedure. Be very parient to go through further to penetrate and give details of evidence of Data 'how it flows in migration'. Please accept if something went wrong and explain with alternative to stakeholders' not to panic and convince 'this will be fixed on within no time'

In order to calm stakeholders you need to do thorough investigation and provide as much information as possible by answering the questions below: 1. What is affected? 2. What are the next steps to get the data fixed? 3. What time will each step take? And of course, you need to keep them posted. It would be also good to do root cause analysis to make sure this will not happen in the future.

If you're data migration just flagged critical issues maybe calm isn't what you are looking for!! Presuming you have been following the migrate early and often approach this is data that has been recently entered or a recently changed sctyps or config. You might need to do manual fixes in source, pre migration or manual catch up activities after migration before go live or you might need to flag some records for next action resolution after go live. Either way you have some unplanned work. Fixing manually in any of these ways will de risk the cut over rather than scrypt or config changes which require testing. It comes at a cost that stakeholders need to decide on and if manual work is chosen, apply resources to.

When data migration tests flag critical issues, it's crucial to keep stakeholders calm. I start by explaining the issue and our plan to fix it, as transparency builds trust. We have a backup plan with a detailed roadmap of steps to address the issue. Regular updates on progress and next steps keep everyone informed. We'll offer live updates and be available to answer questions, maintaining confidence. Our emergency customer service team will guide stakeholders through each step until the issue is resolved, ensuring they feel supported and confident throughout the process.

Every issue either critical or normal is resolvable. Sometime people try to create a situation like panic by defining a minor issue to a critical one Take any issue as just an issue and come with multiple plans to resolve that issue. Discuss all possible solutions with the team and try to get consent on one best solution among all. Explain your final solution to all stakeholders and do needful to close this issue. It will help all as learning for their next assignment.

Connect with stakeholder and explain the issue clearly in simple way. Ask for their insights and criticality on the same and check if their is more to address apart from what has been identified so far. Work on short term and long term solution for the problem. Explain the short term mitigation plan and long term plan for permanent fix. Create a rollback plan and additional validations which we may identify to perform during implementation. Explain that we will be cross validating other in scope data components to make sure smooth migration and avoid similar issues. Take a approval from all the stakeholders and then start working on it. Provide regular update on progress and share the validation reports with stakeholders.

Communication is key! Ensure that the stakeholders are made aware of the situation and what is being done to remediate the issue in the most quick and possible way. Once the issue has been resolved, dissect the cause and work on a viable and potentially fail-safe plan going forward.

Data Migration is a task of well planning with some of the most complex and critical asks. It’s not something, we think and we can do in a single click of a mouse button. In my opinion, It’s depends on certain aspects- 1st part- - What is the need.( Purpose) - Size of data. - Criticality of data & data security. - Environment where Current Data reside. 2nd Part- - First and for most requirement gathering. ( As much could do). - All pre checks and pre image and a back out plan incase of failure. - Take complete backup of existing Data before going any data migration. - Try to opt a well tested robust approach with lesser downtime. - post migration checks and pre image comparisons data match. - good back out plan. With prior taken backup