All use cases Example scenario — not a customer story

Example: moving an agency spreadsheet into Ledrix without mixing brands

This walkthrough demonstrates the admin historical import: map headers, preview, commit. It is not a claim that messy sheets clean themselves. Ledrix does not invent missing IDs.

Admin migrating off Excel or Google Sheets

Scenario setup

Consider an agency with a master sheet: name, phone, brand, closer, amount. Rows for two client brands share one file. The admin wants those contacts in Ledrix on the right brand before closers log in.

Import preview: mapped columns, unmatched brand highlighted, commit disabled until fixed.

1

Step 1 — Clean the sheet first

Export CSV. Fix empty brand names and duplicate headers before upload. Ledrix maps columns; it does not repair garbage rows by itself.

Your export, then upload
2

Step 2 — Admin historical import

Import is admin-only. Closers do not upload the agency sheet. Map headers to lead, order, payment-link, and payment fields. Save the map for the next file.

CSV column mapping
3

Step 3 — Brand: one at a time, or a brand column

Import one brand, or map a brand_name column on plans that allow multi-brand sheets. Unmatched brand names show in preview — they are not silently dumped into a default LLC.

Single-brand or multi-brand sheets (plan-based)
4

Step 4 — Preview, then commit

See duplicates, unmatched brands, and what will be created. Choose merge, skip, or create-new. Commit, or roll back the batch. Row and monthly limits follow the subscription. Basic is a single-brand starter.

Preview before commit
5

Step 5 — Closers pick up assigned records

If the sheet has a closer, map it. If not, assign after import. Sellers still only see their book. Nothing on the row is invented — missing payment IDs stay missing.

Assigned seller panel after import

Build your first separate brand pipeline

14-day free trial, no credit card. Sandbox is shared sample data — a trial is your own workspace.

Questions on this example

Straight answers about how Ledrix is configured — not claimed customer results.

No. Historical import only creates records from data that is actually on the CSV.

No. Historical sales import is an admin tool.

No. CSV is a manual admin upload with mapping, preview, and duplicate handling. Automatic intake is the brand site script or API POST for new leads. Do not treat a spreadsheet upload as ongoing sync from another CRM.