Download the template
Open CSV import in the CRM overview and download the template. Keep the column names as they are, and save the file as UTF-8 CSV with commas as the separator. The dialog offers a preview but no free column mapping. companyName is required; rows with no company name are skipped.
Prepare values correctly
For choice fields, use the internal values from the template or export.
companyName,contactEmail,contactName,stage,source,revenueType,estimatedRevenueMin,tags
Example Inc.,contact@example.com,Alex Example,lead,website,monthly,125,Trade show;Priority- stage
- possible, lead, contacted, demo, proposal, invited, active, or lost. Unknown values and custom stage IDs become lead on import.
- source
- manual, referral, inbound, outbound, website, or event. Unknown values become manual.
- revenueType
- one_time, weekly, 4_weekly, monthly, or yearly. Unknown values become monthly.
- estimatedRevenueMin / estimatedRevenueMax
- Whole euro amounts with no currency symbol; 125 means 125 euros. Don't use thousands or decimal separators.
- tags
- Separate several tags within one cell with a semicolon, for example Trade show;Priority.
Import and check the result
Choose the file, or drag it into the dialog. Check the preview and start the import. Then check the number of imported and skipped rows and any error messages. Open a few new leads and compare stage, contact, and revenue against the file. For a partially successful import, fix only the failed rows; running a full import again creates duplicates.
Know the import limits
Existing leads aren't updated by name or email matching. Ownership isn't imported. Activities, files, and linked projects also aren't part of this import. A direct CSV creation doesn't run stage-change automations or auto-onboarding, even if stage is set to active.
Export the current list
Click CSV export. The crm-leads.csv file contains every lead in the current organization, including contact fields, notes, tags, and selected Lead Engine fields. Board and search filters don't limit the export. Handle the file according to the client and contact data it contains.
Common pitfalls
One-time revenue currently doesn't round-trip cleanly
Export writes oneTimeRevenueMin, while import currently reads a different column name. Check and fill in one-time revenue values manually after import. So an export followed by an import doesn't fully restore the same data.
Export and import aren't a full restore
Ownership, activities, attachments, links, and some Lead Engine fields, among other things, are missing from the CSV round trip. Custom stages are reset to Lead on import.
Frequently asked questions
Can I export only the filtered leads?
The current CSV export doesn't respect the filters. It contains every lead in the organization.
Can I map German column names?
The dialog offers no column mapping. Use the technical column names from the template, and map your source data to them before uploading.
Why did my custom stage become Lead?
Import only accepts the eight default keys. After importing, assign affected leads to the custom stage you want inside the app.