Skip to main content
This is the written version of a video showing how to move an existing database into Leaf360 instead of leaving it in a CRM you don’t like, just because moving thousands of contacts by hand sounds miserable. Prefer to watch it instead? Here’s the video:
For the full reference on the importer, see Import Data. This page just follows the video.

​
Finding the importer

Import Data is in the top right of the header — the spreadsheet icon, tooltipped Import Data (CSV). It handles two kinds of record, each with its own template:
  • Leads — potential borrowers
  • Partners — business contacts, like real estate agents and title companies
This video only covers the Leads and Partners importer shown above. Loans use a separate importer: the upload icon next to Import Data, tooltipped Import or Create Loans.

​
The four-step wizard

1

Choose the type

Pick Leads or Partners. This decides which fields are available and where the records land once imported.
2

Upload your CSV

Only .csv files are accepted. If you’re not sure what columns to use, Download sample CSV on this step gives you a template built from the exact fields Leaf360 recognizes for the type you picked.
3

Map your fields

Every column in your file gets matched to a field automatically where possible. Fix anything mismatched, skip what you don’t want, or turn a column into a custom field.
4

Review and import

A full preview of your rows with the mapping applied, plus bulk controls to fill in anything missing (like lead source or partner contact type) before you commit. Start Import runs it.

​
What happens to contacts you already have

Leaf360 checks each row against what’s already in the system. A row that matches an existing record updates it instead of creating a duplicate — the finished import reports both a Created and an Updated count so you can see which happened.
The wizard doesn’t show you which rows will match before you import, and there’s no way to choose update-vs-create yourself. If that distinction matters for a particular file, import a small slice first and check the counts before running the rest.

​
If something goes wrong

Failed rows are listed by row number with what went wrong, up to the first fifty. There’s no automatic retry — fix those rows in your file and import just that smaller batch again. If an entire import needs undoing, Import History under Data & Integrations in Settings can reverse it, showing exactly what will be deleted and restored first.