What adjustments will you need to make to data architecture and formats to allow access in new cloud environments in view?

Data Migration: Ask This;

TLDR: Ask This;

1. What adjustments will you need to make to data architecture and formats to allow access in new cloud environments in view, and do you have a data migration strategy?

2. Is your organization able to perform data cleansing of legacy data prior to data migration into a new system?

3. Does your organization have resources (DBA, etc) who understand your current database structure and who can extract data into a pre defined file and format?

4. How will you ensure you have a tried and tested migration process and that data dropouts are at a manageable level?

5. Does your organization have standards or protocols in place to monitor and assess the quality of data migration into the system of record?

6. Does the cloud solution have a cost effective data migration process that preserves content structure and integrity and ensures uninterrupted access to critical data?

7. Does the data migration plan include a description of how the legacy data quality will be evaluated?

8. How will you know if the migration has successfully moved the data from the source to the target environment?

9. Does the data migration plan include a description of the test criteria that will be used for verification?

10. Does the data migration plan include a description of how the data migration procedures will be developed and verified?

11. Does the data migration plan include a description of the final (end to end) migration and how verification will be performed?

12. Does the project management team have a good understanding of data migration best practice?

13. Does the data migration plan identify any training requirements that will be needed?

14. Can the data migration occur during regular business hours?

15. Will any metadata be part of the data migration plans?

16. Do you have a data security plan in your data migration strategy?

17. Does the data migration plan identify any downtime that will be required during the migration?

18. If any third party vendors are involved in the data migration, have they been adequately briefed about the migration activity?

19. Are there any other sources of legacy data from which your organization will expect data migration?

20. Who will be responsible for data migration in the future as technology changes?

21. Will multiple data migrations be performed to load data up to a specific date and then a final migration of data right before go live, or will one big bang data migration be performed?

22. What will be the vendors responsibility as it pertains to data migration and data mapping?

23. How many data migration mock runs have been planned and what is the schedule?

24. Does the data migration plan include a schedule of when data migration related activities are expected to take place within the context of the overall development and deployment effort?

25. What resources do you need to make sure the project goes smoothly?

26. Does the data migration plan include a description of the overall strategy and approach to migrating data from the legacy source(s)?

27. Does the data migration plan include business continuity and technical data recovery procedures?

28. Are there any constraints on offshore/offsite requirements that you need to know during data migration?

29. Does the data migration plan include a description of the data transformation process to be used?

30. Is the process for data migration (in/out) one that your organization can plan for/implement?

31. Has a risk assessment or business impact analysis of the data migration project been done?

32. How does your approach to data cleaning and data migration differ from others?

33. Does the migration software support non disruptive data migration (i.e. legacy application continues to operate during the migration) if this is a requirement of the migration?

34. Does the data migration plan include a description of the hardware components needed to complete the migration?

35. What is the planned downtime available for data migration when the cutover happens to the new system from the current system?

36. Does the data that you have match the requirements for data in the new system?

37. How do you ensure that data migration projects at your organization do not lead to data loss or malfunctions and thus endanger your business operation?

38. Do your vendors provide data migration tools and implementation instructions?

39. What tools do you have to handle data migrations, QoS, tiering and thin provisioning to ensure that you are making the most of your investment?

40. Is there a need to control the data migration from a local server or a remote server?

41. Does the data migration plan include a description of the roles and responsibilities for the data migration?

42. Does the data migration plan include a description of the workflow of the data migration scripts?

43. Does the data migration plan identify the entities and attributes to be migrated from each source?

44. Does the data migration plan include the assumptions and constraints on which the plan is based?

45. What happens if data changes on the legacy system after records have already been migrated to the new platform?

46. Does your organization have a data migration test environment with adequate privileges/permissions granted?

47. Is the scope of effort for data migration defined between the vendor and your organization?

48. Is there a data quality specification document to which the final migration results should adhere to?

Organized by Key Themes: DATA, DEVELOPMENT, CLOUD, PROCESS, PROJECT, CLIENT, TEST, SOFTWARE, MANAGEMENT, TECHNOLOGY:

DATA:

Does the product data requirements differ between IS and business perspectives?

Verify that your workforce is performing the functions required for overall execution/management/reporting of contracting programs including preparation, compiling and reviewing statistical contracting data, recommending and providing sound business solutions for a variety of data management issues. 

Will multiple data migrations be performed to load data up to a specific date and then a final migration of data right before go live, or will one big bang data migration be performed?

Certify your group has hands on involvement in Integration tools and frameworks, security frameworks and data migrations. 

Have all risks identified related to data conversion been documented in the project charter?

Be confident that your organization is consulting with the project team to validate requirements as to the use of data and fields identified. 

What was the percentage of performance improvement of application after the data migration?

Drive agile development, migration of processes and data from Business Analysts and Analytics Teams to Technology Supported Platforms. 

Has a schedule been developed that maps out exactly how the conversion/migration is expected to happen?

Establish that your design has hands on involvement writing data quality rules with Business Testing and reconciliation of pre and post clean up. 

What are best practices for developing and maintaining integration project plans?

Secure that your workforce is involved in data architecture, data modeling and adopting best practices and policies in the data management space. 

Have data migration, integration, and archiving business rules been established?

Coordinate with business analysts, and reporting users to understand their data needs, and coordinates the delivery of those requirements with a focus on: data quality, data reuse, consistency, security, regulatory compliance, usage performance, and standards adherence. 

DEVELOPMENT:

How much time would be required from program staff and digital services staff?

Confirm that your workforce works independently on medium to large development projects that require an your organization needs in depth technical and business knowledge in multiple disciplines/processes. 

How do you structure the integration team?

Coach business leaders in the development of resistance management plans. 

Has the risk of each stage of the project been assessed and mitigated and the migration plan signed off by the project Steering Committee?

Support uat by coordinating between business and development team in case of any issues. 

Is data available for a defined period of time after the contract is terminated to support data migration?

Provide design level details (where appropriate) and support development teams in resolution of DevOps related issues. 

Does the cloud provider ensure that metadata remains linked to records during data migration?

Oversee and provide QA for custom development and data migration. 

Are the network, compute, storage and security and compliance requirements all met?

Work with development team and QA to ensure requirements traceability and completeness. 

Do the data experts have access to review the data for quality and consistency?

Participate in review, development and maintenance of security policies. 

What existing metadata do you need in order to find, use, understand and trust the information?

Invest in the development of DB standards and design new systems and procedures to make efficient use of available resources. 

What key risks should IT leadership consider in the planning of the integration?

Participation as key lead on all business development activity for specific client. 

How do you retire one tool and plug another tool easily in the same lifecycle domain without disturbing the current process, and avoiding the large overhead involved in data migration?

Check that your process is involved in an Agile/Scrum software development environment. 

CLOUD:

How do you authorize an employee to access a system or application in the cloud?

Make headway so that your team provides advice, analysis and recommendation on the security products in the cloud security space. 

Does the data migration plan include a description of the overall strategy and approach to migrating data from the legacy source(s)?

Certify your operation has hands on involvement migrating SQL Server data and workloads to the cloud. 

Have test conversions/migrations been performed with a sampling of the data before attempting to apply the solution to the entire system?

Lead cloud and application delivery managers with application migrations from data center to cloud hosting. 

Does the cloud support the identity and authentication mechanism you require?

Support the migration of On Premise users, apps and data to the cloud. 

Are the business owners and other relevant stakeholders involved and participating in the data conversion/migration process?

Secure that your strategy is involved in cloud service offering environment. 

Are the backups stored in a secure location protected from unauthorized users/people?

Warrant that your strategy is analyzing the latest industry trends as cloud computing and distributed processing and beginning to infer risks and benefits of the use in business. 

If any third party vendors are involved in the data migration, have they been adequately briefed about the migration activity?

Warrant that your operation is involved in leading datacenter or cloud migration projects. 

Does the data migration plan include a description of how the data migration procedures will be developed and verified?

Develop experience leading cloud infrastructure adoption and migration efforts required. 

PROCESS:

How much time will you have to test the newly developed functionality that supports your unique requirements?

Develop experience working in various SDLC processes including Agile. 

Has a high level mapping occurred to determine which data elements in the existing system will be converted or migrated to the new system?

Make sure the image export process will be done in four phases. 

How do you execute an effective migration?

Execute due diligence, requirement assessment, process assessment and recommendation. 

Do you need to provide an audit trail for compliance and regulatory approval?

Secure that your company optimizes code performance and processing methods. 

Have you considered transition method and dual reporting needs as part of the data migration strategy?

Guarantee your group includes follow up reporting and building next action process. 

Will interface support be included in the base package, a one time fee, and/or an increase in the recurring system charges?

Create detailed business requirement gathering documents by attending workshops, Create AS-IS and TO-BE business blue printing documentations, determination of gap analysis, functional design and technical designing specifications, business process re-engineering, configuration, custom code specifications, data migration, cut-over, roll-out to real-time production system, change management and post-implementation support. 

Who is involved in the data management process and are all the roles clearly defined?

Verify that your staff is involved in data mapping and data migration processes and tools. 

PROJECT:

Has the right investment been made in the management of change for the teams?

Facilitate change management activities between the project team and IT service groups. 

How do you successfully execute a data migration project?

Work with project teams to execute solutions for client business and technology needs. 

Does your organization have resources (DBA, etc) who understand your current database structure and who can extract data into a pre defined file and format?

Ensure compliance with organization project management policies and standards. 

Do you specify a correction and/or validation to be applied during the data movement process?

Establish that your design is involved in office move or data center migration projects. 

Has the format of any of the disks changed since the target system was last booted?

Manage the project budget, provide change control and ensure business readiness. 

What was done to ensure all data was prioritized appropriately and accurately transferred?

Work to assess and prioritize project management needs for each business area. 

Does the migration software support non disruptive data migration (i.e. legacy application continues to operate during the migration) if this is a requirement of the migration?

Assign and manage work of project team members; provide support and direction. 

Who is involved in the data management process and are all the roles clearly defined?

Make sure your operation is involved in project management methodology. 

Are changes to the system controlled according to its change management process?

Make headway so that your organization is leading monthly meetings with the Resultant Finance team around accounting updates including the portfolio level roll up of projects, deliverables and invoices. 

CLIENT:

How do you measure defects and quality of deliverables by using standard metrics?

Lead and implement change initiatives to deliver effective solutions to the client. 

Does the system allow for reports to be built outside of the system and imported in?

Certify your operation provides regular status updates to PM for client reports. 

What is the plan for integrating service management and governance principles?

Establish and manage relationships with key client executives and stakeholders. 

Are there constraints in the technical capability of the originating and receiving EDRMS?

Support client teams with integration of the SDK and invest in diagnosing issues. 

What should you plan for and expect when it comes to validating the migrated data?

Be sure your workforce (internal) clients do not come to them when the problem is easy. 

Does the migration software support differences in volume size between source and target data?

Define and deploy data migration and replication strategies to meet the (internal) client business support requirements. 

Will the access and use arrangements meet requirements for now and into the future?

Define and deploy data migration and replication strategies to meet the (internal) client business requirements. 

How do you migrate sensitive data from one provider to another?

Work with the client to gather user feedback on implemented functionality. 

Does the project management team have a good understanding of data migration best practice?

Modify use cases and manage tuning for multiple (internal) clients. 

What risks does multi tenancy pose for your organization and how would it affect your cloud architecture?

Ensure your (internal) clients products are used in all types of electronic equipment. 

TEST:

Will there be any data migration from an existing system, spreadsheets, etc?

Make sure your group works closely with Quality Leads, Project Managers and Test Engineers to educate on process and submitting requests for new databases, schemas, migrations, etc. 

How do you check data consistency in the classic general ledger before the beginning of the first test migration?

Execute test plans to ensure quality delivery using test code and unit tests. 

How do you ensure data integrity including data describing context, content and structure when making changes to the computerized systems, software upgrades or data migration?

Warrant that your organization updates test cases based upon approved change requests. 

Does your organization clarify the workflow in requirement and how exporting data from the system would achieve the identification of evidence based programs?

Review test and debug team members work. 

How do you retire one tool and plug another tool easily in the same lifecycle domain without disturbing the current process, and avoiding the large overhead involved in data migration?

Certify your staff is involved in implementing Unit Testing. 

How do you migrate from test to production?

Confirm that your organization is identifying test success and points of corruption. 

Do files get corrupted if the source file server or the network goes down during the migration?

Respond promptly to requests from Validation/Test team for documentation or bug fixes. 

What are best practices for developing and maintaining integration project plans?

Invest in developing and testing internal process improvements. 

SOFTWARE:

How do you know whether your migration setup is correct?

Be confident that your organization is responsible for providing technical support related to software applications and hardware including software installation, service pack updates, migrations, troubleshooting, maintenance, scheduled tasks and SQL data backups. 

If any third party vendors are involved in the data migration, have they been adequately briefed about the migration activity?

Be sure your organization is involved in business intelligence software. 

How do you retire one tool and plug another tool easily in the same lifecycle domain without disturbing the current process, and avoiding the large overhead involved in data migration?

Secure that your strategy is involved in agile software development lifecycle. 

How do you get rid of support contracts for hardware, software and network?

Make sure your process is involved in smart view software installation, software usage and client support. 

Is the information currently held in the legacy system, to be used in your new application?

Consult with (internal) customers to understand the business and recommend best practices in the use of the software. 

Does the data migration plan include a description of the how the data migration scripts will be developed and verified?

Certify your operation determines systems software design requirements. 

Have you planned for a secure, collaborative working environment to be in place?

Be certain that your company participates in development of software user manuals. 

Who are the parties and organizations involved, and are roles and responsibilities clearly defined?

Make sure your staff is involved in software implementation and delivery. 

What happens to any field level data related to a losing record during a record merge?

Be sure your workforce mentors software engineers through code reviews, and hands on design sessions. 

How do you retire one tool and plug another tool easily in the same lifecycle domain without disturbing the current process, and avoiding the large overhead involved in data migration?

Liaison so that your company is involved in version control software as Git. 

MANAGEMENT:

How do you retire one tool and plug another tool easily in the same lifecycle domain without disturbing the current process, and avoiding the large overhead involved in data migration?

Secure that your strategy is involved in program and project management fundamentals. 

Does the import/export cover all the required information content and all associated metadata?

Understand data management and import/migration, automation rules, link tracking. 

Who is involved in the data management process and are all the roles clearly defined?

Certify your workforce is involved in project management tools and methodology. 

Do procedures include a testing and approval process that must be followed prior to installation?

Follow risk management and compliance procedures. 

What are the major reasons for keeping the legacy systems your organization is currently planning to retain?

Make sure your team is working group charters, management plans. 

Has the best human and/or software approach been developed to maximize quality and minimize expense?

Perform risk management to minimize possible project impacts. 

How do you measure defects and quality of deliverables by using standard metrics?

Ensure you provide exceptional management and technology solutions that deliver practical and innovative results to your (internal) clients. 

If any third party vendors are involved in the data migration, have they been adequately briefed about the migration activity?

Secure that your process is involved in cmo management including selection. 

TECHNOLOGY:

Does the solution provide immediate time to value or does it require a data migration?

Secure that your workforce expands adoption of existing technology, where appropriate, to leverage enterprise solutions that meet or exceed business partner demands. 

How do you look toward measures that depend on that data from outside your current organization?

Be sure your group understands client business functions and technology needs. 

Is a central console needed to manage data migrations across multiple servers?

Ensure technology solutions align with business needs and strategic goals. 

Has a specification document been developed that maps out exactly how the converted data will look?

Develop innovative solutions to complex business and technology problems. 

What will be the vendors responsibility as it pertains to data migration and data mapping?

Ensure your organization is a leading information technology provider for overarching, state and local organization departments. 

How many clients will be utilized to push the migration of files from the source servers?

Serve as an integrator between business needs and technology solutions. 

Do you have to wait until the end of the migration before going live with the new system?

Liaison so that your design applications consultants have expertise in a specific technology environment.