But here's the catch: it looks like simple drag-and-drop work. It isn't. Results vary widely based on field mapping, data formatting, and which template you actually use.
This guide covers when to use templates, what you need before starting, the exact steps, the variables that determine success, and the mistakes that trip up most teams.
TL;DR
- Template-based imports bulk-upload or update CRM records from a spreadsheet matched to your CRM’s field structure
- Best fit for one-time migrations and bulk updates—not continuous syncing
- Success depends on clean data, correct field mapping, and CRM-specific rules for lookups and picklists
- Most failures trace back to formatting and duplicates, not the tool itself
How to Import CRM Data Using Templates
Step 1: Download and Prepare the Correct Template
Salesforce, HubSpot, and Dynamics 365 all provide entity-specific templates for Leads, Contacts, and Accounts. Each one matches the target object's schema exactly.
Using a generic spreadsheet instead of the CRM-generated template is a leading cause of mapping errors. Salesforce's Data Import Wizard auto-maps as many fields as it can, but unmapped fields simply don't get imported: they're silently skipped, not flagged as errors.
Before you start:
- Check for hidden validation or dropdown sheets in Excel templates — these define accepted picklist values
- Confirm the template matches your CRM edition (fields vary by plan)
- For Dynamics 365, automatic mapping needs file names that match record-type display names and headers that match field labels
Step 2: Clean and Format Your Source Data
This is where most import problems start. Formatting mismatches cause more failures than any other single factor.
- Phone numbers: HubSpot expects the format
+[country code][number], with extensions written asext[number] - Dates: HubSpot supports month-day-year, day-month-year, and year-month-day, but your file must match whichever format you select during setup
- State/country fields: Match values exactly to what the CRM's picklist expects
- Duplicates and emails: Remove duplicate rows and validate email addresses before mapping
- UTF-8 encoding: Save non-English text as UTF-8. HubSpot requires this for foreign-language characters; skipping it produces garbled text after import
Step 3: Map Fields and Configure Import Settings
Match each spreadsheet column to its CRM field. Pay close attention to lookup and relationship fields.
Lookup fields are unforgiving. In Salesforce, an Account name referenced in a Contact import must already exist in the CRM, or the import fails or creates an orphaned record.
Salesforce's Data Loader can use an External ID instead of a Salesforce record ID for related-record lookups, but the External ID must be unique and populated first.
For updates rather than new records:
- Salesforce: Choose add, update, or add-and-update in the wizard
- HubSpot: Provide a unique identifier (Record ID, Contact Email, or Company Domain Name), with Record ID taking precedence
- Dynamics 365: Map primary key fields for record matching during import
Step 4: Run a Test Import and Validate
Import 50-100 records first. Every CRM vendor recommends this. It's the cheapest way to catch mapping errors before they scale to thousands of rows.
After the test batch:
- Review the import log or report for errors, skipped rows, or partial failures
- Check HubSpot's downloadable error file for error codes and affected records, or Salesforce's Bulk Data Load Jobs status
- Fix the source file or mapping based on what you find
- Only then run the full import
Skipping this step is the single most common, and most avoidable, cause of messy CRM data.
When Should You Use Templates & What You Need Before Importing
Templates work best for bulk, one-time work: migrations, seasonal list uploads, or standardizing existing records. They're not built for real-time or high-frequency syncing.
Volume matters too. Salesforce's Data Import Wizard is designed for under 50,000 records. Beyond that, Salesforce recommends Data Loader, which handles up to 150 million via Bulk API 2.0. Dynamics 365 documentation recommends keeping imports to 20,000 rows or fewer per file.
Before you start any import, confirm you have:
- A recent CRM backup
- Cleaned, deduplicated source data
- Documented field mappings
- All required fields populated
- Admin-level import permissions
- Familiarity with entity-specific rules
If your migration involves complex object relationships or six-figure record counts, a template alone probably won't cut it. That's when dedicated migration tools or managed services start paying for themselves.
Key Parameters That Affect Import Results
Import outcomes hinge on a handful of controllable variables, not the CRM platform you picked.
Field mapping accuracy. Incorrect mapping silently populates the wrong fields or leaves them blank. In Salesforce, unmapped columns simply don't import: no warning, no error. The result is unusable segments and broken reports weeks later, when someone finally notices the data gap.
Data encoding and formatting. Mismatched encoding corrupts non-English text. Inconsistent date or phone formats trigger validation rejects. HubSpot, for instance, rejects number-property values containing non-numeric characters outright.
Lookup and relationship integrity. Lookup fields require exact matches—spelling, punctuation, everything. A typo in an Account name creates an orphaned record instead of linking to the right one.
Duplicate detection rules. CRMs apply matching logic based on email or name combinations. Poorly configured rules either block valid imports outright or create redundant records that pollute your reporting.
Common Mistakes & Troubleshooting While Importing
Most import problems repeat across teams. They're preventable once you know what to look for.
| Mistake | Likely Cause | What to Check |
|---|---|---|
| Skipping the test import | Rushing to finish | Always validate 50-100 records first |
| "Columns empty" errors | Blank columns/rows beyond the data range | Trim unused cells, re-save as CSV |
| Lookup values not matching | Typos, abbreviations, missing CRM records | Pre-create lookup records or use CRM-sourced dropdowns |
| Garbled non-English text | File saved in ANSI/ASCII instead of UTF-8 | Re-save the CSV in UTF-8 encoding |
A quick example: adding a new column to a previously exported Dynamics 365 template, even one extra field, can cause the re-import to fail entirely. Leave the template structure intact unless you also update the import mapping.
Alternatives to Template-Based Import
Templates aren't always the right call, especially for recurring or complex needs.
Common alternatives include:
- Native or third-party migration tools (Salesforce Data Loader, KingswaySoft for Dynamics 365): Stronger for large datasets, complex relationships, and GUID-preserving migrations, with a steeper learning curve and more setup time
- API-based integrations: Best for ongoing automated syncing; HubSpot's Imports API maps columns to properties programmatically, but you need developers to build and maintain it
- Managed data services: Fit teams without bandwidth to clean, map, and validate in-house; CRM Migration and Modernization services move records, activities, pipelines, attachments, and reports from spreadsheets or legacy platforms with cleaning and mapping handled end-to-end
For manufacturers, industrial distributors, and B2B service firms without a dedicated ops team, value extends past migration day. Gushwork also builds and configures CRM systems with automated tracking and lead-to-revenue dashboards, so imported data supports accurate lead tracking and reporting as growth campaigns scale.
Conclusion
Template-based CRM import works when three things line up: clean source data, accurate field mapping, and a validated test batch before the full run.
Most failures come from preparation gaps, not the CRM tool itself. Whether you stick with templates, move to a migration tool, or bring in a managed service depends on your data volume, relationship complexity, and internal bandwidth. Match the method to the job, and the import stops being the bottleneck.
Frequently Asked Questions
How do I import data into my CRM?
Most CRMs provide an Import or Data Management tool. Upload a CSV or Excel file matched to a template, map the columns to CRM fields, then run the import in batches.
How do I extract data from a CRM?
Use the CRM's export feature (often labeled "Export to Excel" or "Dynamic Worksheet") to pull existing records into a spreadsheet for editing or backup.
How do I import data in Salesforce?
Use the Data Import Wizard for under 50,000 records, or Data Loader for larger volumes. Map CSV columns to standard or custom fields and always validate with a test batch first.
How do I migrate data to Dynamics 365?
Use the Import from CSV/Excel feature, mapping primary key fields for record matching. You can optionally retain source GUIDs for continuity across systems.
What file formats work best for CRM template imports?
CSV (UTF-8 encoded) and Excel (.xlsx) are the most widely supported formats. UTF-8 is required whenever your data includes non-English characters.
Can template imports update existing records instead of creating duplicates?
Yes. Most CRMs offer an "update existing records" or matching-key option (email, domain, or record ID) to enrich existing data rather than create duplicates.
