Back to Documentation
Data Import Formats
Purpose
Get clean, ready to import files for your systems. Use these templates as is or ask for a custom map. For help, email henry@primechasedata.com.
Supported Systems
CRM & Sales Tools
- Salesforce
- HubSpot
- Generic CSV (any CRM)
- Google Sheets
- JSON API
Warehouse Targets (on request)
- BigQuery
- Snowflake
- Redshift
- Postgres
- S3
Global File Rules
Encoding:UTF-8
Delimiter:Comma, header row required
Dates:ISO 8601 (2025-08-21T14:30:00Z)
Currency:3-letter code (USD, KRW)
Phone:E.164 (+12025550123)
Booleans:true or false
Nulls:Blank or null, not N/A
Structure:One object per file unless noted
Quick Start
1Pick your CRM below and download the matching template headers
2Tell us which fields are required in your org
3Send any existing import templates you already use
4We return a sample of 50 rows for validation
5We deliver the full file after approval
CRM Import Templates
Salesforce Imports
Objects covered: Lead, Account, Contact. Deal imports available if you want us to open opportunities.
Lead Import Headers
External_Id__c,FirstName,LastName,Email,Phone,Title,Company,Website,Street,City,State,PostalCode,Country,LinkedIn_URL__c,Department,Industry,NumberOfEmployees,LeadSource,PCD_Verified_Date__c,PCD_Source_System__c,PCD_Intent_Topics__c,PCD_Account_External_Id__c
Recommended Setup
- • Create custom fields marked External ID and Unique for External_Id__c
- • Turn on duplicate rules that prefer External IDs over fuzzy email matches
- • Use Data Import Wizard for small files, Data Loader for 50k+ rows
- • After Lead import, use standard conversion flows or map directly to Contact/Account
Sample Data
Lead.csv Example Rows
c6f2f…,Jin,Park,jin.park@example.com,+821012345678,Marketing Manager,Acme Co,https://acme.co,KR,Seoul,Seoul,https://linkedin.com/in/jinpark,Marketing,Software,500,2025-08-18T10:00:00Z,places_api,ACME-KR 1a9b4…,Sara,Kim,sara.kim@example.com,+12025550123,Director,Acme USA,https://acme.com,US,VA,Manassas,https://linkedin.com/in/sarakim,Marketing,Software,1200,2025-08-18T10:00:00Z,web_form,ACME-US
JSON API Payload Example
{ "lead_id": "c6f2f…", "first_name": "Jin", "last_name": "Park", "email": "jin.park@example.com", "phone": "+821012345678", "title": "Marketing Manager", "company": "Acme Co", "country": "KR", "verified_date": "2025-08-18T10:00:00Z", "source_system": "places_api", "account_external_id": "ACME-KR" }
Validation Checklist
Before Import
- Headers match your template
- Required fields present for each object
- Emails lowercase and verified
- Phones pass E.164 checks
- Countries use ISO-2 codes
- Dates are ISO 8601 with Z for UTC
- No hard returns inside cells
- No leading or trailing spaces
- Duplicate rows removed
Common Errors & Fixes
- Bad date format → Convert to ISO 8601
- Country names instead of ISO-2 → Map to codes
- Non-unique External IDs → Regenerate and retry
- Emails with uppercase/spaces → Normalize to lowercase, trim
- Comma in field without quotes → Re-export with proper quoting
Delivery Options
CSV Files
Zipped if over 50k rows. Direct download link provided.
Google Sheets
Shared view-only. Easy preview and download options.
JSON API
REST API with OAuth 2.0. Real-time data sync.
International Support
- • We can include both Hangul and romanized names
- • KRW and USD supported in the same file
- • Address fields follow country-specific formats
- • Phone fields stored in E.164 international format
Security & Privacy
- Only fields listed in your data dictionary are delivered
- Files move over TLS encryption
- Files at rest are encrypted
- Access is least privilege and removed on request
Need Custom Formats?
If you need a custom format or mapped export for a different tool, email us with your target template and we will return a mapped sample.
Contact henry@primechasedata.com