Said It Here

How to migrate data without breaking deep object dependencies

Moving data between systems fails when hidden third-party apps, undocumented user customizations, and deep record associations break the import order. This prevents teams from successfully transferring systems without losing critical linkages and system configurations.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Using existing migration tools such as Gearset, Copado, Serpent, or Flosum
  2. 2
    Writing custom scripts with the assistance of AI coding tools
  3. 3
    Hiring an MSP or specialized migration company
  4. 4
    Using third-party migration tools like MigrationWiz
  5. 5
    Conducting extensive inventory and testing periods
  6. 6
    Bringing in external training for staff adaptation
  7. 7
    guessing essential features and unexpected dependencies
  8. 8
    asking others who have recently implemented sales management systems for advice

In their words

Unedited, most upvoted first, each linked to the thread it came from.

the challenge is that we are very deeply invested in the Google Workspace ecosystem.source ↗

No_Introduction_3472 · r/sysadmin · 27 upvotes

My main worry is what happens to the processes and departments connected to the CRM.source ↗

I have a bad feeling that we are going to repeat the mistakes of the past once again.source ↗

Fancy_oalexneydew802 · r/CRM · 6 upvotes

The biggest issue is maintaining record associations and moving the right objects in the right order. Dependencies can go really deep on objects.source ↗

AccountNumeroThree · r/salesforce · 1 upvotes

The hidden SSO and third party app stuff is what usually bites you.source ↗

glitchykitten681 · r/sysadmin · 1 upvotes

Users build things and don't tell us.source ↗

Agent_DekeShaw · r/sysadmin · 1 upvotes

Where this came up

People with this problem also raised