53,640 Salesforce Files, 770 HubSpot Tickets, and One Migration Lesson

https://hackernoon.imgix.net/images/XCho2ckaEzTt48zZ189BpNTBZDY2-zs33awi.png

I went into a Salesforce-to-HubSpot migration expecting schema mapping and CSV cleanup to be the difficult parts. They weren't. The harder problem appeared when we reached historical support data: 53,640 case-related files had to remain understandable and traceable, while only 770 corresponding support tickets existed in the destination at that stage of the migration.

A CSV can move properties. It does not automatically preserve the relationship between a record, its attachments, the physical files in an export, and the object that represents that record in another platform.

The solution was to stop treating the files as a pile of attachments and build an explicit identity layer first: source case number → source record → exported file → destination ticket.

That manifest became the control plane for the rest of the migration.

I Thought the CSVs Would Be the Hard Part

The migration started as most CRM migrations do.

Inventory the...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE