Customer Import
Import existing customer records safely from a CSV file using preview, field mapping, duplicate review, and final confirmation.
Updated
Overview
Customer Import lets you bring existing customer records into FBM from a CSV file instead of creating customers one at a time. FBM uses a preview-first import process: uploading a CSV does not immediately create customer records. You can review the rows, map CSV columns to FBM fields, check the source data, and confirm the import only after you are satisfied with the result.
When to use this
- Move customer data from another business system into FBM.
- Start using FBM when you already have an existing customer list.
- Import customers from a supported accounting, CRM, field-service, or generic CSV export.
- Migrate a cleaned customer list into your FBM company account.
Before you start
- Prepare and review the CSV before uploading it.
- The audited Customer Import screen accepts CSV files up to 5 MB.
- Check obvious data-quality problems such as incomplete customer names, phone numbers in the wrong column, or address data stored in the wrong fields.
- Remove duplicate customer rows from the source CSV before the final import.
Supported source selections
| Source Program | Observed support |
|---|---|
| Generic CSV | Supported. |
| Wave | Supported. |
| QuickBooks | Supported. |
| Xero | Supported. |
| Jobber | Supported. |
| Housecall Pro | Supported. |
| FreshBooks | Supported. |
| Square | Supported. |
| Zoho Books | Supported. |
Step-by-step
-
Open Customer Import
Open the Customer Import page from FBM Settings. -
Select the source program
Choose the system that produced the CSV. If the file is not from a specifically listed system, use Generic CSV. -
Upload the CSV file
Select the CSV containing the customer records. FBM parses the file and prepares the rows for review. Uploading the file does not yet create customer records. -
Review the preview
Confirm that the expected rows are present and that names, email, phone, and address information appear in sensible source columns. -
Map CSV fields
Match each CSV column to the correct FBM customer field. Do not map a source column unless it actually contains that type of information. -
Check duplicates
Review the source data again for duplicate customers. If duplicates exist, clean the source CSV and repeat the preparation with the corrected file. -
Confirm the import
Proceed with final confirmation only when the preview and mapping are correct. The audited workflow states that customer records are created only after final confirmation.
Key mapping fields
| FBM Field | Purpose |
|---|---|
| Customer Name | Customer or company name. |
| Customer email address. | |
| Phone | Primary phone number. |
| Address | Street address. |
| City | City. |
| Province / State | Province or state. |
| Postal Code | Postal or ZIP code. |
| Notes | Additional customer information. |
| Customer Type | Customer classification/type. |
Important: remove duplicate records first
The CSV file should not contain duplicate customer records before the final import. Clean duplicate rows in the source CSV first. Do not rely on the import process to decide which duplicate record should be kept.
Example scenario
A flooring company exports its customer list from another system. The file contains customer name, email, phone, address, city, province, and postal code. The company first removes duplicate customer rows. In FBM, the user selects the appropriate Source Program, uploads the CSV, reviews the parsed rows, maps each column to the correct FBM field, and confirms the import only after the preview is correct.
Important notes
- Uploading a CSV is not the same as completing the import.
- Treat preview and field mapping as validation steps.
- Clean duplicate source records before final confirmation.
- A well-prepared source file reduces cleanup after migration.
- If a column does not clearly correspond to an FBM field, do not guess during mapping.
Common mistakes
| Mistake | Why it matters | What to do |
|---|---|---|
| Importing a CSV that still contains duplicate customers | It creates unnecessary cleanup and ambiguity. | Remove duplicate source rows before final confirmation. |
| Mapping the wrong columns | Information can be stored in the wrong customer fields. | Review the preview and map only clearly matching columns. |
| Assuming preview created the customers | Preview is a validation stage, not the final write. | Complete the explicit final confirmation when the data is correct. |
| Uploading the wrong export file | The preview and mapping will not represent the intended customer list. | Verify the source program, file contents, and preview before confirmation. |
What happens next
- Imported customers become part of the company's normal customer records after final confirmation.
- You can then work with customer details, contacts, addresses, projects, invoices, activity, portal features, ledger information, collections, and statements where applicable.