01 / The existing evidence
An example, no upload
This page accepts no file and processes no personal data.
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak CRM · Import
A spreadsheet of contacts is mapped column by column to your CRM fields. You see possible duplicates before the import, not after.
Start Peak CRM for freeSample CSV · no upload · nothing is imported
CSV fileYour spreadsheet
Peak CRMThe target fieldperson.emailA readable field path as an example. No transfer.
| CSV file | Peak CRM property |
|---|---|
person.email | |
| First name | person.first_name |
| Last name | person.last_name |
| Company | company.name |
| Durum | crm.classification |
The mapping shows the translation. Only a test in your workspace shows what actually arrives.
02 / Preview before import
A good import changes nothing you have not seen beforehand.
In the product you upload your spreadsheet. On this page there is only an example.
Each column gets its target field; unclear columns stay marked.
Existing contacts are shown before anything is taken over.
Trust needs clarity
01 / The existing evidence
This page accepts no file and processes no personal data.
02 / Your check
The real import runs in your workspace, after sign-in and with your confirmation.
03 / The clear limit
Existing contacts are not replaced without asking. You decide on every duplicate.
The next step
Start Peak CRM and map your own spreadsheet step by step.
Start Peak CRM for freeCheck in your workspace what actually arrived.
No. This page only shows a sample CSV. The real import runs in your workspace after sign-in.
Possible duplicates are shown before the import. You decide on each one.
Typically name, email and company. Unclear columns stay marked until you map them.