Over the last month, I've created a new org that our company will be migrating to relatively soon. No issues with the data migration itself or re-creating objects, fields, flows, etc. However, I'm struggling to conceptualize a roadmap to successfully migrate Dropbox for Salesforce from our existing SF org to our new SF org.
For anyone that's not familiar with Dropbox for Salesforce, files for each SF record are stored within an independent Dropbox folder. Within this folder, an auto-generated .txt file (recordid.sfdb) creates a link between Salesforce & Dropbox. This link enables users to view/add/edit/delete Dropbox files for a single record from within Salesforce while viewing that record's page.
Our company has roughly 5,000 records with existing folders that are stored in Dropbox. After migrating these 5,000 records into the new org, the link between each SF record and Dropbox is now broken because every record has a new record ID (old_recordid.sfdb vs. new_recordid.sfdb).
I should note that I have already installed/configured Dropbox for Salesforce in the new org. Also, I'm able to successfully link a single record from the new org to it's existing Dropbox folder by deleting the old linking .txt file, then manually adding a new .txt file named new_recordid.sfdb. Therefore, I know a solution is within reach.
Any ideas on how I could address this issue in the form of a bulk action? There's no telling how long it'd take me to manually drag and drop the remaining 4,999 txt's to each of their corresponding Dropbox folders.
Open to all ideas. Thanks
#Dropbox #Org Migration #Salesforce Developer #Salesforce #Data Management #Automation
You could probably automate this by generating a CSV mapping old to new record IDs and using a script or integration tool to rename the .txt files in bulk. I’ve seen teams handle similar migrations with Skyvia since it can sync Salesforce data with cloud storage like Dropbox and apply transformations based on record ID mappings. Might save you from a lot of manual work.