Import your data
Nobody wants to retype four hundred customers. If you have them in a spreadsheet, another CRM, or QuickBooks, import them.
CSV import is Growth and up (bulkImport).
Where the importer lives
On the list page for whatever you’re importing — Customers for customers, Locations for properties. It moved there deliberately: importing customers belongs where customers are, not buried in Settings.
Importing customers
Export from wherever the data is now
A CSV with one row per customer. Don’t spend time cleaning it up first — it’s easier to see what needs fixing after the preview.
Open Customers and choose Import
Map your columns
Tell LawnLedger which of your columns is the name, which is the email, and so on. It guesses from the headers and is usually close.
Check the preview
This is the step to slow down on. The preview shows what will be created and flags rows it can’t read.
Import
What to expect
- Duplicates are detected by name and email — you’ll be asked what to do rather than ending up with two of everyone.
- Bad rows are skipped, not fatal. You get a list of what didn’t import and why, and you can fix and re-run just those.
- Properties can come in the same file if each row has an address; they’ll attach to the customer on that row.
From QuickBooks
If you’re coming from QuickBooks, connect it instead of exporting a CSV — see QuickBooks sync. It brings customers across and keeps them in step afterwards, which a one-time CSV can’t.
Tips
- Import customers before properties, and both before jobs. Later imports attach to earlier records; the other order leaves orphans.
- Do a ten-row test file first. Ten wrong rows are a nuisance; four hundred are an afternoon.