A go-live date should be in place at this time. The amount of time for migration or integration that was gathered in the testing data transfer phase can be used to work back from the go-live date to determine how much time should be allotted for final deployment. Final deployment often will happen at night or over a weekend. This will allow for some extra time to adjust for any issues that might arise.
Once the time frame is determined, a plan should be in place to lock users out of legacy or integrated systems when the final deployment is started. If it is determined that final deployment will take an extended period of time, it is common to allow users access to legacy systems in a read only fashion during this period.
Data migrations and integrations have many components that need to be considered, including the best practices during the migration and integration processes, design documentation, and the risks taken. If the risks are considered and mitigated, best practices taken, and the proper documentation is detailed, the process will go smoothly.
- Copying Scribe Target Steps Using DTSEEdit (Blog)
- Scribe Queue Publisher vs. Query Publisher for Dynamics CRM (Blog)
- Format Phone Numbers with Leading Zeros via Scribe Insight in CRM (Blog)
- Activity Parties and Dynamics CRM to CRM Migrations with Scribe (Blog)
- 11 Data Migration Tips (Blog)
- Dynamics CRM Using Scribe Insight and an Easy Way to Link Accounts and Contacts when Migrating Data (Blog)