How do you handle migrating email threads and attachments? Is it even possible?

ellaq · 2026-07-29T08:55:58Z

Alright, I'm diving into a migration project that's giving me serious pause, and I'm hoping this community has some battle-tested wisdom. We're planning a move from a legacy on-premise CRM (think something like a highly customized SugarCRM) to a modern cloud platform (Salesforce, in our case). The core objects—Accounts, Contacts, Opportunities—feel manageable. But the real hair-pulling challenge is the historical email correspondence. We have *years* of email threads, with attachments, logged against contacts, leads, and opportunities. This isn't just "nice-to-have" data; for our support and renewal processes, the context in those old emails is critical. My big, looming questions are: * **Is full-fidelity migration even a realistic goal?** Can we truly move nested threads with all recipients, timestamps, and attachments intact into the new CRM's email-related objects? Or are we destined for a compromise? * **What are the practical, real-world approaches you've taken?** I've heard a spectrum of strategies, from: * The "Big Bang" – using middleware or custom scripts to map and insert every single email and attachment as native CRM records. * The "Archive & Link" – exporting all emails as PDFs or PSTs, storing them in a secure cloud bucket (like S3 or SharePoint), and then just migrating a hyperlink to that archive within the corresponding record. * The "Fresh Start" – only migrating emails from open opportunities or the last X years, and accepting the historical loss. The technical concerns are massive. Attachment size limits, API timeouts, preserving the "linked-to" record relationship, and the sheer volume are daunting. Then there's the cost: some migration tools charge per "record," and each email *and* each attachment might count as separate records! I'm especially curious about what **broke** in your attempts. Did your new CRM's email rendering look wrong? Did links to attachments break? Were performance issues crippling after the migration? This feels like one of those make-or-break decisions that doesn't get enough airtime before signing the contract. What do you wish you had known, or what clever workarounds have you seen succeed?

Page 3 / 3 Prev

CRM Migration Stories

Last Post by Andrew8 1 hour ago

31 Posts

30 Users

0 Reactions

7 Views

RSS

Andrew8

(@andrew8)

Estimable Member

Joined: 2 weeks ago

Posts: 101

30/07/2026 4:11 pm

Simple external ID, stored as a field. We used the original email's SHA-256 hash as both the external ID and the S3 object key.

Why a hash? It's deterministic. Even if your export runs twice, the same email generates the same ID and key, preventing duplicates. The link is just a presigned URL to `s3://archive-bucket/{sha256}.eml`.

No internal tool needed. Your migration script calculates the hash, pushes the file, writes the ID to Salesforce. Retrieval is a straightforward API call from a Lightning component.

Numbers don't lie.

ReplyQuote

Page 3 / 3 Prev