Help Center
DocsImporting Data & CRM Migration
Import data from CSV files or migrate from 20+ competing CRMs with auto-detection and field mapping
Supported Entity Types
Import 8 different entity types from CSV, Excel, JSON, or ZIP files.
Core Entities
- Companies — Company records with names, contact info, addresses, industry, and custom fields.
- People — Person/contact records with names, emails, phone numbers, and company associations.
- Opportunities — Deals with values, stages, probability, and linked companies or contacts.
Extended Entities
- Activities — Calls, emails, meetings, and notes linked to companies or people.
- Tasks — Task records linked to projects with status, priority, and assignees.
- Products — Product catalog entries with pricing, SKU, and billing period.
- Tickets — Support tickets with status, priority, and category.
- Projects — Project records with stages, budgets, and timelines.
Supported CRM Migrations
Migrate from 20+ competing CRMs with auto-detection and optimized field mapping.
Full Migration Support (Tier 1)
Complete field mappings, value transformations, and auto-detection for:
Basic Migration Support (Tier 2)
Field mappings and detection without value transformations:
Generic Import (Tier 3)
Listed for recognition with fuzzy field matching:
Import Wizard
Two paths to import: Magic Import (auto-detect everything) or manual CRM selection.
The import page offers two ways to start:
Magic Import
Drag and drop your file. The system automatically detects which CRM it came from, identifies the entity type, and maps all fields. You go straight to the review screen.
Manual CRM Selection
Click your current CRM from the grid. This applies CRM-specific field mappings and value transformations for the most accurate import.
Upload your file
Upload a CSV, Excel (.xlsx/.xls), JSON, or ZIP file. Multiple files can be uploaded at once. ZIP files are automatically extracted. Maximum file size is 10MB.
Review field mapping
The system auto-maps columns to Laureo fields using preset mappings (for known CRMs), synonym matching, and fuzzy matching. Green dots indicate high-confidence matches, yellow for medium confidence, and red for unmapped fields. Adjust any mapping using the dropdown.
Choose duplicate handling
Select how to handle duplicate records: Skip (keep existing), Update (overwrite with imported data), or Create New(import as separate records).
Import
Click Import to start. Large imports process in the background — you can safely navigate away and will be notified when complete. Check progress in the Import History tab.
File Requirements
Supported formats and specifications.
- CSV — Standard comma-separated values, UTF-8 encoding, header row required.
- Excel — .xlsx and .xls formats. First sheet is imported.
- JSON — Array of objects, or nested format (Salesforce, Close).
- ZIP — Contains CSV/Excel/JSON files. Each extracted file is detected and imported separately.
- Size limit — 10MB per file, 10,000 rows maximum per import.
Duplicate Detection
How duplicates are identified during import.
- Companies — Matched by account number (exact), then company name (case-insensitive).
- People — Matched by email address + company combination.
- Opportunities — Matched by deal name + company combination.
- Activities — Matched by subject + date + entity link.
- Tasks — Matched by title + project.
- Products — Matched by SKU (exact), then name (fuzzy).
- Tickets — Matched by ticket number.
- Projects — Matched by name + company.
Import History & Rollback
Track past imports and undo if needed.
The Import History tab shows all past imports with their status, record counts, and source CRM. Completed imports can be rolled back within 24 hours — this deletes created records and restores updated records to their pre-import state. Rolling back requires typing “UNDO” to confirm, as any manual changes made after the import will be lost.
Data Health Assessment
Pre-import data quality check.
Before importing, the system runs a health assessment on your data. This shows a readiness score (green/yellow/red) based on completeness, data quality, duplicate risk, and relationship integrity. Recommendations are provided to fix issues before importing.
Troubleshooting
Common issues and solutions.
- CRM not detected— If auto-detection fails, manually select your CRM from the grid. Tier 3 CRMs use generic fuzzy matching.
- Fields not mapping correctly— Use the dropdown to manually set each field mapping. Fields prefixed with underscore (_) are internal transform targets.
- Date format issues— The system supports ISO 8601, US (MM/DD/YYYY), EU (DD/MM/YYYY), and month-name formats. If dates parse incorrectly, check for ambiguous formats (e.g., 01/02/2024).
- Salesforce custom fields (__c)— Fields ending in __c are detected as Salesforce custom fields. Map them to Laureo custom fields or skip them.
- Import times out— Large imports process in the background. If the page seems stuck, check the Import History tab for progress.
- Company not found for people import— Import companies before people. Enable “Create missing companies” in import options to auto-create companies from the people file.