Skip to content
Docs menu

Import from Funnel

Bring an existing Funnel database into Venom. The export format (one CSV per table or one JSON file), how contacts become People, what is matched and what is created, and what a re-import does.

View .md

If you used Funnel before, /funnel/settings → Import from Funnel brings your data into Venom Funnel and People. Choose Preview to see counts and warnings without writing anything, then Import. Only the people with a write role can import. The files are read in your browser session and the server; nothing leaves Venom. The limit is 3 MB per import: import the tables in parts if you have more.

The export format

Export each table from your Funnel database as CSV with a header row (for example \copy (select * from deals where org_id = '…') to 'deals.csv' csv header), or put the tables in one JSON file as { "deals": [ … ], "contacts": [ … ] } (Funnel's own { "tables": { … } } wrapper also works). CSV files are matched by name: companies.csv, contacts.csv, pipelines.csv, stages.csv, deals.csv, deal_stage_history.csv, products.csv, deal_items.csv, activities.csv. Use Funnel's column names; extra columns are ignored and every table is optional.

Table Columns used
companies id, name, domain, address, notes
contacts id, company_id, first_name, last_name, email, phone, title, tags, source, lifecycle, notes
pipelines id, name
stages id, pipeline_id, name, position, probability, kind, rot_days
deals id, pipeline_id, stage_id, title, value_cents, currency, company_id, contact_id, owner_id, source, expected_close, lost_reason, created_at, closed_at, stage_entered_at, position
deal_stage_history deal_id, from_stage_id, to_stage_id, changed_at
products id, name, sku, unit_price_cents, currency, description
deal_items deal_id, product_id, name, quantity, unit_price_cents, discount_pct
activities kind, subject, body, deal_id, contact_id, created_at, due_at, done_at

What happens to each table

  • Companies become People companies (matched by name, case-insensitive).
  • Contacts become People. A contact whose email or phone matches a person you already know is matched, not duplicated, so the deal links to the person you have. Others are created with their email and phone as handles, the tags, the Funnel source and lifecycle in "how we met", and the notes. You choose who can see them: the whole organisation (the default, since they are business contacts) or only you.
  • Pipelines and stages are matched by name, then created. A new pipeline missing a won or lost stage gets one.
  • Deals keep their value, currency, dates, status (from the stage), lost reason and position, and link the contact and company. The Funnel user id in owner_id becomes a member if you map it (one funnel user id = email per line); otherwise you own the deal. Deals are visible to the organisation.
  • Stage history is kept, so the conversion and velocity reports are right for old deals. A deal with no history rows gets one entry for its current stage.
  • Products and lines are matched by SKU then name, and lines keep their quantity, price and discount. The deal's value is the value in the export.
  • Activities on a deal become the deal's activity (a call, meeting, email or note). A Funnel task becomes a note on the deal ("To-do: …, due …, done"): importing a Funnel database does not create Tasks issues in bulk. An activity on a contact only becomes an interaction on that person.

Deals are tagged with their Funnel id, so importing the same export twice adds no deals. Contacts are matched again by email and phone. Rows that cannot be imported (a deal whose stage is not in stages.csv, a contact without a name or email) are skipped and listed as warnings.

Funnel's goals, saved views, custom fields and web forms are not imported; recreate them in Funnel settings.