Your HubSpot import just finished, the new record count came in short of your row count, and the error file is full of codes like DUPLICATE_ALTERNATE_ID that nobody on your team has seen before. Every one of those errors names a column, a rule, and sometimes a different system entirely, and each one has a specific fix once you know how to read it. This guide shows you how to decode the errors HubSpot reports after an import or a Salesforce sync, trace each one to the system that caused it, and catch the silent failures that never show an error at all.
What You’ll Find Inside
Fix your next failed import without guesswork. The guide covers where HubSpot reports errors, a three-question method for reading any of them, decoded email, duplicate, field, limit, and permission errors from real client imports, the Salesforce sync errors that need an admin on the other side, the silent failures that never trigger an alert, and a four-layer method for confirming an import or migration worked.
On the File imports tab, hover over the import, click More, and select Download error file to get a CSV with each error code, the reason, and the original row values.
You can delete the records an import created from that import's records tab, but changes the import made to existing records can't be reversed that way.
Who This Is For
Marketing ops, RevOps, and CRM admins who run imports into HubSpot
Anyone holding a HubSpot error file and unsure which rows to fix first
Teams with a HubSpot and Salesforce integration showing errors in Sync Health
Teams in the middle of a migration who need to confirm every record arrived
.png?width=1080&height=1080&name=CC%20Square%20Image%20(12).png)
.png?width=1080&height=1080&name=Hero%20Image%20Templates%20(51).png)