File Migration Strategy
GENERAL OVERVIEW
In Salesforce we have a fixed structure for managing documents based on the Document
and Document Version
data tables which are connected to the Account
, Contact
and Opportunity
objects.
In Sharepoint we have a flat folder structure for managing documents that are linked to Salesforce records.
A directory in Sharepoint is configured specifically for Salesforce use.
Each
Document Version
Record has its own folder which will link to the a component in Salesforce where a file can be viewed and uploaded.In Salesforce we combine files from
Document Version
folders so that all files can be viewed from the parentDocument
record.
FOLDER NAMING
Folder naming needs to align with attributes on the records in Salesforce, which creates a challenge when setting up the folders before data migration has been completed.
To support an efficient data and file migration process:
We will have an
External ID
field on the related parent record (Account
,Contact
orOpportunity
) which is populated with the ID of the corresponding record from FlowLogic.We will have a standard Salesforce ID which will be available on all
Account
,Contact
andOpportunity
records.Sharepoint Folder Name
is a formula field onDocument
records with logic to the effect:IF((External_ID__c != NULL, External_ID__c & ' - ' & Document_Type__c, Salesforce ID & ' - ' & Document_Type__c)
OBJECT | NAMING CONVENTION | NOTES |
---|---|---|
|
*Parent ID relates to Contact, Account, Person Notes records. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TESTING
We need some sample records in FlowLogic to manually move into Salesforce to test our migration strategy.
Document
andDocument Version
records will be created as part of the test migration process.We potentially need the Microsoft partners to create folders for us based on a list of
External IDs
that we provide for them out of FlowLogic.We need to validate that we can accurately create
Document
andDocument Version
records with the data migration process - we needDocument Type
,External ID
and related parent record (Account
,Contact
orOpportunity
) to be accurately identified in the data.
RELEVANT DOCUMENTS
FILE NAME | PURPOSE | FILE/LINK |
---|---|---|
Document Fields Version: 3.0 | Provides a mapping of FlowLogic documents to |
|
Document Fields Version: 3.1 | See above |
DELIVERY TIMELINE
ITEM | OWNER | COMPLETION DATE | NOTES |
---|---|---|---|
File Repository Sharepoint to Salesforce Integration Completion | Vertic | Jun 2, 2023 |
|
Document Type Mapping - Draft | MySupports | Jun 16, 2023 |
|
Document Type Mapping - Completion | MySupports | Jun 23, 2023 |
|
Document Creation Rules included in Data Migration Package | Vertic | Jun 23, 2023 |
|
Document and Document Version Record creation in Salesforce - Test Run | Vertic | Jun 23, 2023 |
|
Document Export provided to Efficient Chips to enable naming convention | Vertic | Jun 23, 2023 |
|
Document Folder Creation in Sharepoint - Test Run | Efficient Chips | Jun 30, 2023 |
|
Updates/Fixes | Everyone | Jul 4, 2023 |
|
Document Folder Creation in Sharepoint - Full Run | Efficient Chips | Jul 7, 2023 |
|
File Distribution | My Supports & Efficient Chips | Jul 11, 2023 |
|
DataNova to provide go-live database | MySupports | Jul 11, 2023 7 PM AEST |
|
Document Export to be provided to MySupports | Vertic | Jul 11, 2023 8 PM AEST |
|
Document Fields File Merge Completion | MySupports | Jul 11, 2023 10 PM AEST |
|
Go-Live Document Record Creation | Vertic | Jul 11, 2023 11 PM AEST |
|
Go-Live Folder Connection Testing | Vertic & My Supports | Jul 12, 2023 |
|
Document Folder Creation in Sharepoint - Delta Run | Efficient Chips | Jul 12, 2023 |
|