ESILaw Legacy to ESILaw 360 Migration Process:

• Client completes order form (https://dyedurham.ca/esilaw-360-order-form/) for 360 indicating the Migration selection. (it also has a field for legacy audit number)
• Finance will look up their current contract term/expiry date. (If necessary, get approval from Bryce Szela to move forward with migration - he needs to know how long of a contract did they sign for and how much is still outstanding).
• ALL MIGRATION FEES ARE WAIVED (unless otherwise advised by Sales). NO Quote Required.
• Coordinator will create a DEPLOYMENT ticket and assign to deployment team by using the "ESILAW::Legacy to ESILAW Deployment Ticket - CREATE" and then the "ESILAW::Legacy to ESILAW Deployment Ticket - OPEN" macro. 

DEPLOYMENT PROCESS:

• Request for Legacy migration is passed to Deployment
• DEPLOYMENT will reach out to customer and explain process and use the "ESILAW::Migration from Legacy to 360 reply to customer" Macro to coordinate the migration date and provide the checklists:
  
  • ESILaw 360 Migration FAQ.pdf
  • 360 Migration Preparation & Post Migration Checklist.pdf
• DEPLOYMENT confirms date availability with Migration Specialist and adds the date migration is to be completed to SharePoint calendar
• Deployment reaches out to customer to obtain latest backup via macro esiLaw Legacy Backup Instructions.
• Migration Specialist completes the migration in the evening
  • If there are errors during migration Priyanka will document issues in a email and Deployment follow up with firm the following morning to review the errors and coordinate resolution
  • If no errors, DEPLOYMENT will confirm with the firm that the migration was successful, and they can complete the Post Migration Checklist
• Once the firm confirms that the migration was successful the ticket can be closed, and all future support will be provided through Customer Service

PCLaw Conversions:

• Coordinator would receive Order Form  https://esilaw.com/buy-now/ with conversion indicated from PCLaw to esiLaw
  Note: Customer must have PCLaw version 14 or above for conversion to be done. If they are V13, it cannot be completed.
• ALL MIGRATION/CONVERSION FEES ARE WAIVED (unless otherwise advised by Sales). NO Quote Required.
• DEPLOYMENT ticket is created using the "ESILAW::PCLaw to ESILAW Deployment Ticket - CREATE" MACRO.  Once the ticket is created, use the "ESILAW::PCLaw to ESILAW Deployment Ticket - OPEN" MACRO and save as Open.
  • DEPLOYMENT team will connect with customer, provide checklists and discuss needs and schedule on the calendar: https://econveyance.sharepoint.com/sites/ESILAW_TEAM/Lists/Esilaw%20Calendar/Migrations.aspx
  • Once the conversion is started, the customer cannot access their PCLaw database to make changes or amendments (only run reports) and should not access ESILaw360 until complete.

Cosmolex, Ammicus (or Other) Conversions:

• Coordinator would receive new order form with the request for conversion
• Migration Specialist may need to review customer database to evaluate
• ALL MIGRATION/CONVERSION FEES ARE WAIVED (unless otherwise advised by Sales). NO Quote Required.
• DEPLOYMENT ticket is created and deployment team to coordinate conversion date (for larger firms, schedule conversion on Fridays) with Dorin and communicate this back to the customer
  • Migration Specialist needs to connect to the workstation on the day prior to conversion date to access the Data.
  • Once the conversion is started, the customer cannot access their Cosmolex/Ammicus database to make changes or amendments (only run reports) and should not access ESILaw360 until complete.