Fix Address Errors Before CRM Import: State, ZIP, and Country Codes (2026)

💡 Quick Answer

CRM address field rejections come from four sources: state full names instead of ISO 3166-2 abbreviations, ZIP codes with leading zeros stripped by Excel, country values that don't match the platform's accepted format, and address lines split across the wrong number of columns.

Salesforce and Zoho require ISO 3166-1 alpha-2 country codes (US, GB, DE). HubSpot accepts country names but requires exact spelling. State fields vary: most CRMs require the two-letter USPS abbreviation, not the full state name.

The fix: Standardize address fields in your CSV before upload using a local cleaning tool — not after the import rejects 340 records.

Root cause: Address data accumulated in spreadsheets over time uses inconsistent conventions. No CRM importer tolerates that variation.

---

⏰ FAST FIX (90 Seconds)

If your import failed on address fields:

1. Open your CSV in SplitForge Data Cleaner
2. Select the State column — run Find & Replace to convert full state names to USPS two-letter codes (Illinois → IL, California → CA)
3. Select the Country column — standardize to ISO 3166-1 alpha-2 codes (United States → US, United Kingdom → GB)
4. Check your ZIP column — confirm leading zeros are present for CT, MA, ME, NH, NJ, NY, RI, VT, and other Eastern states
5. Re-import the cleaned file — address field rejections are the most consistently fixable CRM error type

---

TL;DR: Address field rejections are some of the most predictable CRM import errors because they follow a short list of root causes: state name vs abbreviation, country format mismatch, leading zeros stripped from ZIP codes, and address line column count mismatch. Each is fixable in minutes with a local data cleaner before upload. Data Cleaner →

---

You exported 5,000 contacts from your marketing platform and prepared the import file over two hours. You upload to Salesforce. The progress bar reaches 68% — then stops. The import completes with 340 failures. The error log says: State: Illinois (invalid), Country: United States of America (invalid), PostalCode: 06103 (invalid format).

None of these are data errors. They're format errors. The underlying data is correct — Illinois is a real state, the United States is a real country, 06103 is a real ZIP code. But Salesforce expects IL, US, and a five-character string it can validate against its postal code table.

Most address cleaning and standardization tools upload your file to a remote server for processing. A contact import file containing names, physical addresses, and postal codes falls under GDPR Article 5(1)(c)'s data minimization principle — uploading customer location data to a third-party service for format correction creates a processing step that may be unnecessary. If the tool retains file contents, GDPR Article 28 processor obligations may apply, requiring a Data Processing Agreement. SplitForge cleans address fields entirely in Web Worker threads in your browser. Your file never reaches any server. Verify in Chrome DevTools → Network tab — no outbound file transfer occurs during cleaning.

Each address format error type in this guide was validated against Salesforce, HubSpot, and Zoho CRM import requirements, March 2026.

---

📋 Table of Contents

• The Four Address Fields That Break CRM Imports
• Platform Address Requirements at a Glance
• Step-by-Step: Standardize Addresses Before Import
• ZIP Code Leading Zeros: The Silent Killer
• Common Address Errors and Exact Fixes
• Additional Resources
• FAQ

---

What Address Import Errors Actually Mean

"State: Illinois (invalid)" — The CRM requires the USPS two-letter state abbreviation (IL), not the full state name. Applies to all US states and territories.

"Country: United States of America (invalid)" — The CRM requires ISO 3166-1 alpha-2 format (US) or sometimes the full English name (United States), but not abbreviations (USA) or extended names (United States of America).

"PostalCode: 06103 (invalid format)" — The leading zero was stripped when the file was opened in Excel, converting 06103 to 6103. The CRM validates ZIP code length and format — a four-digit ZIP fails.

"Street2 field exceeds maximum length" — Full addresses pasted into a single column were split with a comma delimiter, but the split logic left too many characters in one of the resulting fields.

Address silently missing after import — Column header doesn't match the CRM's expected field name. The importer skipped the column rather than rejecting the row.

---

The Four Address Fields That Break CRM Imports

1. State / Province Field

Most CRMs require the two-letter USPS state code for US addresses. Full state names, abbreviations with periods (Calif., Mass.), and numeric FIPS codes are typically rejected.

❌ BROKEN — state column with mixed formats:
state
Illinois
calif.
New York
TX
Washington State
Wash.
N.Y.
Pennsylvania

Salesforce rejects: "Illinois", "calif.", "Washington State", "Wash.", "N.Y."
HubSpot rejects: "calif.", "Washington State", "Wash.", "N.Y."
All CRMs accept: TX (already correct in the sample above)

FIXED — USPS two-letter codes:
state
IL
CA
NY
TX
WA
WA
NY
PA

2. Country Field

Country format requirements differ significantly by CRM. Salesforce uses ISO 3166-1 alpha-2 codes if State/Country Picklists are enabled, and free-text if not. HubSpot accepts full English country names. Most CRMs reject abbreviations like USA, UK, and UAE — these are not valid ISO codes.

3. ZIP / Postal Code Field

ZIP codes for Eastern US states begin with zero — Connecticut (06xxx), Massachusetts (01xxx–02xxx), Maine (04xxx), New Hampshire (03xxx), New Jersey (07xxx–08xxx), New York (10xxx–14xxx), Rhode Island (02xxx), and Vermont (05xxx). Excel strips leading zeros from numeric columns on open, converting a valid five-digit ZIP to a four-digit string that fails CRM validation.

See our guide on fixing leading zeros disappearing in CSV files for the full explanation of why Excel does this and how to prevent it.

4. Address Line Column Count

A common export format combines the full address in one column: 123 Main St, Suite 400, Springfield, IL. Most CRM importers expect separate columns for Street1, Street2 (optional), City, State, and ZIP. Importing the full string into the Street1 column fails field length validation or populates everything into a single field.

---

Platform Address Requirements at a Glance

PLATFORM SPECIFICATION SOURCE Platform: Salesforce CRM Source: Salesforce Help: State and Country/Territory Picklists URL: https://help.salesforce.com/s/articleView?id=sf.admin_state_country_picklists_overview.htm Verified: March 2026 Next re-verify: June 2026

Values in this table reflect official documentation at the verification date. Platform requirements change with product updates — the official source is authoritative.

---

Step-by-Step: Standardize Addresses Before Import

Step 1: Audit Your Address Columns

Before cleaning, identify what you have. Open your CSV and check: How many address-related columns exist? What are the header names? Are state, city, ZIP, and country in separate columns, or combined?

If your address data is in a single column, use Split Column to separate it before standardizing the individual fields.

Step 2: Standardize State Codes

Use Find & Replace to convert full state names and non-standard abbreviations to USPS two-letter codes. This is the most common address import failure and takes under two minutes to fix.

1. Open your CSV in Data Cleaner
2. Select the State column
3. Run Find & Replace for each state full name: Illinois → IL, California → CA, etc.
4. Catch edge cases: Calif → CA, N.Y. → NY, Washington State → WA

Step 3: Standardize Country Codes

For Salesforce with State/Country Picklists enabled, convert all country values to ISO 3166-1 alpha-2 codes. For HubSpot, convert to full English country names. The ISO 3166-1 standard is the authoritative reference.

Common corrections: USA → US, United States of America → US (Salesforce) or United States (HubSpot), UK → GB, UAE → AE.

Step 4: Fix ZIP Code Leading Zeros

If your file was opened in Excel at any point, the ZIP column may have lost leading zeros. Open the CSV in a text editor (not Excel) to check raw values. For the affected rows, prepend the missing zero: 6103 → 06103, 1234 → 01234.

For large files, use Data Cleaner to pad the ZIP column to five characters using a leading-zero fill rule.

Step 5: Validate Before Import

Run the cleaned file through Data Validator to confirm all address fields match expected formats before upload. Check remaining errors against your platform's import requirements.

---

ZIP Code Leading Zeros: The Silent Killer

Excel treats ZIP codes as numbers by default when opening a CSV. It strips leading zeros silently — no warning, no error. The ZIP 06103 becomes 6103. The ZIP 01234 becomes 1234. Both fail CRM postal code validation.

❌ BROKEN — ZIP column after Excel opens the CSV:
zip
6103
1234
2101
10001
90210

The first three ZIPs lost their leading zero. 10001 and 90210 are unaffected
because they start with a non-zero digit. Eastern state ZIPs are the most
common victims.

FIXED — ZIP codes restored to five-digit format:
zip
06103
01234
02101
10001
90210

This is one of the more frustrating address errors because the underlying data was correct in the original system. Excel introduced the error on open. See our full guide to leading zeros disappearing in CSV files for the complete prevention workflow.

---

US vs International Address Handling

The workflow in this post is US-centric by design — USPS codes, ZIP formats, and ISO alpha-2 are primarily US pain points. International address structures differ significantly, and CRMs handle them with varying degrees of tolerance.

In a 5,000-contact import from a US-based SaaS company with a mix of domestic and international contacts, address-related import errors affected approximately 8% of rows — most commonly ZIP format errors on Eastern US addresses and country code mismatches on UK and Canadian contacts.

Where this workflow breaks down for international data:

UK postcodes, Canadian postal codes, and German PLZs are alphanumeric. CRMs that validate ZIP/postal code format against a US ZIP pattern (5 consecutive digits) will reject these as invalid — even though the underlying data is correct. If your import file contains international contacts, set the postal code column as text format before export to prevent any numeric auto-formatting, and confirm your CRM's postal code field type supports alphanumeric input before importing.

Multi-line addresses (common in UK and German business addresses: building name, floor, street) don't always fit cleanly into Street1 and Street2. If a contact's address requires three lines, the third line typically has to be appended to Street2 or dropped — review which information is most useful for your use case before deciding.

---

Common Address Errors and Exact Fixes

---

Additional Resources

Official Address Format Standards:

• USPS Publication 28: Postal Addressing Standards — Official US postal address format specification
• ISO 3166-1: Country Codes — International country code standard (alpha-2, alpha-3, numeric)
• ISO 3166-2: Subdivision Codes — State and province code standard

CRM-Specific Address Requirements:

• Salesforce State and Country Picklists — Salesforce address field configuration and picklist values
• HubSpot Country Property Values — Accepted country name formats for HubSpot imports

Data Quality:

• GDPR Article 5: Data Minimization — Principle limiting unnecessary third-party processing of personal data

---

FAQ