...
Use the XML import methods, detail for the import tool and file formats provided here: Data Migration Utility. Below is a quick list of items that may give an outline of processes to be completed during the migration:
Collect Support Phone Numbers
Finance:
Development:
Operations:
Legacy System:Decommissioning
Provisioning services
Email notification servers
Legacy BillingImport Process
Update/verify time-sensitive views, views with date calculations
Backup previous XML import folders
Backup EngageIP Prod Database config
Backup existing current staging database(s)
Import/Stage legacy data to intermediate database(s)
Verify staged data is complete (transactions from most recent dates included)
Copy any staged/static XML to import folder
Restore prod database to dev environment to prep for import
Turn off DAL Logging
Import base data as required
Verify base data
Complete XML imports
Complete each stage of import, backup and verify as you go
Generate equipment import CSV
Verify Inventory Locations/Bins
Import Equipment
Run Post-Import Scripts if needed
Restore DAL Logging
Backup and push database to production
Perform exception reporting and deliver to CSRs for manual correctionPost-Deployment Tasks
Notify management/stakeholders
Enable provisioning services
Confirmation Email for Go-Live to end users
Notify customers of changes/portal location/other relevant info
Do a preliminary accuracy check to ensure customers have been entered into EngageIP Billing:
Can you look them up?
Can you view their packages and services?
Are next bill dates correct?
Are base fees correct?
Is the status listed correctly?
Are their contacts filled out?
Do you see a full list of transactions?
If the above step is successful, proceed to validating reports for number of users in the system etc:
Do the reports accurately reflect the number of users imported?
Are the balance totals correct, both at the customer level and on reports?
...