02 - Creating a Migration Playbook

02 - Creating a Migration Playbook

When a surgeon goes into an operating room, they have a written-down plan that describes exactly what they are going to do.  This plan provides confidence and assurance that the project will be done correctly and ensures that no step can be lost or forgotten.

When you work on a migration, you should have a similar Playbook.  This stores information about the back up and restore, as well as a record of every action taken on the database tables as a part of the migration.  This allows you to audit your work and know exactly what was done.

At the top of your playbook you should store information about your migration project in a comment block.  Below is a template we suggest you use for all your playbooks.

  1.  /*
  2. Migration Path: [SOURCE] => [DESTINATION]
  3. Quoted Amount:
  4.  
  5. Migration Specialist
  6.             Name:             
  7.             Email:             
  8.             Mobile:           
  9.  
  10. Point of Contact (POC)
  11.             Name:             
  12.             Email:             
  13.             Mobile:                       
  14.                         Ensure you're in their contacts so they will recognize your call and answer.
  15.  
  16. Dest Account Manager
  17.             Name:             
  18.             Email:             
  19.             Mobile:                       
  20.  
  21. Source Credentials
  22.             URL:  
  23.             Username:      
  24.             Password:       
  25.  
  26. Dest Credentials
  27.             URL:  
  28.             Username:      
  29.             Password:       
  30.  
  31. Document Caches
  32.             RAW:             
  33.             HUMAN:                   
  34.  
  35. Initial Extract
  36.             Date:               
  37.             Duration:        
  38.  
  39. Delta Extract
  40.             Date:               
  41.             Duration:        
  42.  
  43. Data Summary
  44.             RUN THIS QUERY
  45.            https://help.universalmigrator.com/portal/en/kb/articles/other-obtaining-record-counts-for-all-tables
  46.     AND PASTE THE RESULTS HERE        
  47.  
  48. --Special Requests
  49. */

  



    • Related Articles

    • 01 - Creating a Migration Workspace

      Prior to scoping a migration, you should create a migration workspace for the prospective project on your migration workstation. This folder structure will contain notes and important information about the project that you will add to as you discuss ...
    • 03 - Scoping your First Migration

      When a patient needs an operation, a good surgeon gets as much information as possible from the patient before recommending a course of action or providing a quote. By taking this approach, the surgeon can provide a better, more informed experience ...
    • Migration Type: Delta Migrations

      A "Delta" migration is necessary when you migrate some data now and some data later. To do a Delta migration, please follow the steps below after you have complete the initial backup and restore. 1. Create the "Phase 2" Backup Using Universal ...
    • 01 - Configuring a Migration Workstation

      Location Matters Please refer to this article for information on where a migration workstation should be provisioned. Best Practice: Choosing the Right Location for a Migration Workstation For Multiple Concurrent Migrations If you intend to do lots ...
    • 02 - Configuring a Migration Workstation (For One Concurrent Migration)

      Recommended Location A migration workstation configured this way can be located in any of the following locations: in your office in your data center on the same network as the customer's server (if they are moving from an on-premise application) ...