Contacts & Companies
Contacts are the people you sell to. Customers are the organisations they belong to. Every email, call, meeting, and note lives on a timeline attached to both, so the full relationship history is always one click away.
On this page
Contacts and customers
How DealJourney models people and the organisations they work for.
A contact is a person. It holds their name, email, phone, job title, and any custom fields you add. A customer is the organisation the contact works for: a company, a public entity, a household, whatever your business sells to.
Contacts are linked to customers through an organisation mapping, which means one contact can be associated with more than one customer. This is useful for consultants who work across multiple client organisations, or for sellers who follow a buyer as they move between companies.
Both records have full activity timelines and can be assigned to an owner. Customer records also store billing-relevant fields (address, VAT or tax ID, website, industry) that flow straight onto quotes and invoices without rekeying.
The contact timeline
Every interaction with a contact, in one chronological view.
The timeline on a contact or customer record aggregates every interaction DealJourney knows about: emails sent and received, calls logged, meetings scheduled, notes added, tasks completed, tickets opened, opportunities created. Anything synced from Gmail or Outlook lands here automatically.
You can add entries manually (logging a call, jotting a note) and filter the timeline by type when you're looking for something specific. When a contact moves between customers, the timeline follows the contact rather than being orphaned.
Importing contacts via CSV
Upload a spreadsheet, map columns, review before committing.
The import flow accepts CSV files with any column layout. Upload the file, match each column to a DealJourney field, and preview a sample row. The import runs in the background and reports back with a full result (created, updated, skipped, failed) with a row-level reason when something doesn't land.
Existing records are matched by email (for contacts) or name (for customers), so re-importing an updated list extends what's there rather than duplicating.
Exporting data
Get your contacts out of DealJourney whenever you need to.
Every list view (contacts, customers, opportunities, leads, tickets, invoices) supports a CSV export with column selection. Custom fields are included when you tick them. Exports are generated synchronously for small sets and asynchronously for larger ones.
Your data is yours. The public REST API gives you a second, programmatic route if you want to mirror data into a warehouse or another tool rather than exporting manually.