Import & export (CSV)

Sales

Preb works with plain CSV files so you can pull data out for retargeting or your CRM, and bring historical payments in. This page covers both directions.

Exporting from Global Data

Every table tab of Global Data — Contacts, Setting, Calls, and Deals — has an Export button. It downloads a CSV of exactly what the table shows right now:

The same rows. Your search, quick filters, advanced filters, and active Smart View all apply. Filter first, then export, and you get precisely that segment.
The same columns, in the same order. Whatever you've made visible in the Columns menu is what lands in the file — custom fields and form answers included. The contact's name and email always lead, so every export is usable as an audience or import file on its own.
The same sort.

A Smart View is a saved export recipe

Because the export mirrors the current view, saving a Smart View also saves an export you can re-run any time: apply the view, click Export. Filter to Disqualified contacts, export, and upload them to Meta as a Custom Audience to retarget the leads who didn't qualify for a call.

Export history

Next to the Export button, the ▾ menu lists the recent exports for that tab — what was downloaded, how many rows, when, and by whom. Click any entry to run it again: the export re-runs with the exact same filters, columns, and sort it had originally, against your current data.

That makes a weekly pull trivial — export once, then re-run it from history every week. Preb keeps the latest 25 exports per tab.

Importing transactions

If you have past sales recorded elsewhere — a spreadsheet, another CRM, an old payment processor — you can bring them into Preb as revenue. The import attaches payments to one existing contact, so open that contact first.

Open the contact

Find the person in Global Data and open their card. (Importing adds revenue to an existing contact — it doesn't create new contacts.)

Click Import transactions

You'll find the button on the card's Deals tab.

Choose your CSV file

Pick the file from your computer.

Map your columns

Tell Preb which of your columns is the amount, date, and so on. It auto-guesses based on the headers.

Review and import

Check the preview, then import. Each row becomes a closed deal on this contact.

Each imported row creates a closed deal plus a transaction, both counting toward that contact's revenue immediately.

CSV format

You don't need exact column names — you map your own columns to Preb's four fields during import:

Field	Required?	Notes
Amount	Required	A positive number.
Date	Required	When the payment happened.
Currency	Optional	A 3-letter code; blank uses your workspace default.
Description	Optional	A short label for the payment.

Because you map columns yourself, a CSV exported from almost any tool will work — just point Preb at the right columns.

Tips & limits

Exports are capped at 10,000 rows per file — they're built for audiences and segments, not bulk data dumps. Tighten your filters if you hit the cap.
Transaction import handles up to 1,000 rows and a 1 MB file at a time. Split larger files.
Imports are forgiving. Each row is checked on its own — valid rows import while any rows with problems (a missing amount, an unreadable date) are skipped and listed so you can fix them.
The payments ledger isn't exportable — exports cover the four table tabs. Individual payments live on the Deals tab's Transactions rail.

Mistaken imports are reversible

If you import the wrong file, you can delete the imported transactions from the contact's card. (Payments tied to a recorded Sale outcome are protected — see Deals & revenue.)