Broker Forge Help

Importing customers from CSV

Bring your existing book over from a spreadsheet without losing data or creating duplicates.

Updated May 19, 2026 · 5 min read

Most brokers come in with a spreadsheet — Excel, Google Sheets, or an export from another platform. The CSV import handles all three, with AI-assisted field mapping so you don't have to rename a single column.

Before you start

  • Save your spreadsheet as .csv (UTF-8). Excel: File → Save As → CSV UTF-8.
  • Make sure each row is one customer (or one meter if you track meters separately — see below).
  • One column should hold either the legal business name or a contact name. Without that, the importer refuses the file.
Don't clean the columns first

The mapping step lets you point any of your columns at any of our fields. There's no need to rename headers or reorder columns. Bring it in as-is.

Step-by-step

  1. Open the importer

    From Customers, click Import in the top right. You can also jump directly to the CSV import page.

    The Import button lives next to New customer.
    The Import button lives next to New customer.
    Open CSV import
  2. Upload your file

    Drag the .csv onto the upload zone or click to browse. The importer reads the first 200 rows for preview — your whole file is processed once you confirm.

    Drag-and-drop or click to upload.
    Drag-and-drop or click to upload.
  3. Map your columns

    Broker Forge guesses the mapping using column headers and a quick scan of the data — a column of values like 75201 or 77002 becomes ZIP, BR1234 becomes PUCT, and so on. Review the guesses and adjust any that look wrong.

    AI-suggested mappings on the left, your columns on the right. Override any guess.
    AI-suggested mappings on the left, your columns on the right. Override any guess.
  4. Confirm and import

    The importer shows you a preview of the first ten rows mapped, plus the count of new vs. duplicate customers (matched by legal name + service address). Click Import to commit.

    Final result screen — counts of imported, skipped, and errored rows.
    Final result screen — counts of imported, skipped, and errored rows.

Tips & gotchas

Duplicate detection

The importer matches on legal name + ZIP. If you have two locations of the same company at the same ZIP, the second one will be flagged as a duplicate. Add a suffix to the legal name (e.g. "ACME — Dallas Warehouse") to keep them distinct.

ESI IDs need 17 digits

ESI IDs in Texas are 17-digit numbers. If you've stored them with dashes or in a column formatted as "number with commas," the importer will reject those rows. Export the column as text and re-import.

One meter per row vs. one customer per row

If your spreadsheet is one row per meter (common when exporting from a TDU or supplier portal), use the Group by option in the mapping step. Pick the column with the parent legal name and the importer will create one customer with N meters underneath.

Related

Was this article helpful?

Related articles

Customer fields, accounts, and ESI IDs
What every field on a customer record means and why ESI IDs unlock the rest of the workflow.
Working the pipeline (Kanban)
Drag deals through stages, set close dates, and watch your forecast update in real time.
Your first quote, end to end
From new customer to sent proposal in one sitting. The full motion, with no skipped steps.
Edit this article on GitHub