This document details the standard data migration strategy plan form FlowLogic to Salesforce.
DATA MAPPING
A sample data mapping can be found in the sheet linked below.
https://docs.google.com/spreadsheets/d/1klOOWE1e9NAK_r_fSvb2QWZ8CUyoxatgfI1-qfgRFts/edit?usp=sharing
DATA MIGRATION PACKAGE BUILD
On a SQL Server instance in Vertic’s Amazon Web Services account, we will build a package which maps the FlowLogic database into Salesforce and, once built, can be executed to perform data runs into Salesforce. The ultimate aim of this build is to enable an efficient ‘go-live’ production run which ensures operational downtime is as minimal as possible and to ensure data quality, which is tested during the initial run and subsequent patches, is maintained in the ‘go-live’ migration.
The identified primary migration areas which will also have relationships and child data areas to be included in the build.
Data Migration Package Build - Base Package
Data Migration Package Build - Sites
Data Migration Package Build - Staff
Data Migration Package Build - Clients
Data Migration Package Build - Service Agreements, Funding Sources & Funding Claims
Data Migration Package Build - Suppliers
Data Migration Package Build - Funding Administrators
DATA RUN EXECUTION
Data runs will be performed to ensure the data package that we build is successfully meeting the requirements of the MySupports team and to allow review and feedback.
We will perform our data runs in the MySupports production Salesforce environment, where we have the data space to complete full data runs.
Execution of Initial Test Migration Run
Based on the initial analysis and data mappings provided we will perform the initial data run.
Expecting will be around 70-80% data accuracy.
Execution of Further Data Patches & Feedback
Completed based on feedback of the initial data run.
Further transformations and data analysis to be completed.
Expecting that this will increase data accuracy to 90-95%.
Execution of Production Data Run
Go-live data run when data is fully tested and approved.
Expecting minor gaps that are discovered during first few days of go-live where we can run further patches directly into production if required.
DATA MIGRATION TIMELINE
The proposed timeline below details the actions required leading to go-live.
ITEM | TIMING | NOTES |
|---|---|---|
Data Source to Target Mapping | MONTH 1 | Fields to map have been identified. We need to provide the Salesforce mapping fields and transformations. |
Package Build | MONTH 2 | Based on the agreed mappings. |
Initial Test Migration Run | MONTH 2 | Refreshed database from FlowLogic required. |
File Migration Sample Run | MONTH 3 | |
Further Data Patches & Feedback | MONTH 3 | Team to provide feedback. |
Production Run | MONTH 3 | Refreshed database from FlowLogic required. |