One thing I’ve noticed across CRM and ERP integrations is that the initial sync isn’t usually the hard part.
The difficult problems tend to appear days or weeks after a project is marked complete.
Some examples:
1. Duplicate records after retries
A failed webhook is retried without proper idempotency, creating duplicate invoices or contacts.
2. Currency rounding differences
Small rounding discrepancies accumulate until finance starts questioning invoice totals.
3. Partial refunds
Native integrations often handle full refunds well but break down when only part of an order or invoice is refunded.
4. Deleted or merged CRM records
A contact or company is merged or deleted in HubSpot, but downstream systems continue referencing the old ID.
5. API rate limits
Everything works during testing, but production traffic triggers rate limiting and intermittent failures.
6. Expired authentication
Access tokens expire silently, and the first indication is a failed sync discovered days later.
None of these are particularly difficult to solve individually.
The challenge is that they’re edge cases that rarely appear in demos or initial testing, yet they consume a disproportionate amount of delivery time once a project is live.
I’m curious:
Which post-launch integration issue has consumed the most time on your projects?