Keep the account and contact record

Open an account and the whole relationship is already on the page

It's Monday, your call with Northwind starts in four minutes, and nobody has looked at them since spring. The account opens on a brief: where it stands with each of your products, open next actions and how many are overdue, open opportunities, known contacts, the last recorded activity and the day it was first seen.

Behind the brief sit the next actions, a timeline that puts website activity, meetings, stage changes and support outcomes in one order, the opportunities, the research evidence, the documents and the buying committee.

An account you're working for two products keeps two standings, never folded into one status. Qualified for one and turned down for the other is two facts, and a single badge would get one of them wrong.

One person, one record, and every product keeps its own yes

A contact is one record for your whole organization, keyed on their email address. What differs by product — the owner, the lifecycle stage, the marketing consent — lives on that person's link to each product, so a yes for one product is never a yes for another. Consent starts as unknown, and unknown is never read as permission.

Moving someone forward through the lifecycle takes no explanation. Moving them backward does: the database asks for a written reason, whatever screen the change came from. Undo is polite too. If a teammate changed the stage after you did, your undo stops and says so rather than flattening their change.

Deals run on rules too. A deal enters an active stage only once it has an owner and a next action with a due date, it's won only from negotiation, and once closed it stays closed — a deal that comes back to life starts as a new opportunity. Every move writes a history row naming who moved it and any reason they gave.

Your old CRM's records come across with a dry run first

Start from your current CRM's export or a spreadsheet. CSV, TSV and Excel files are read, and exports from several common CRM, commerce, billing, email and support tools each get a reader that knows their columns.

Columns are matched by their headers, then a dry run shows what every row would do — create, update, flag a duplicate, exclude, or stop on a conflict — before anything is written. A person can change a row's decision right there. Approval comes next, and apply runs as one database transaction: it finishes completely or not at all, running it again changes nothing, and a file already imported into a product is refused the second time.

Imported contacts arrive with consent unknown. A row counts as opted in only when the file carries both the opted-in state and where that consent came from, and one common CRM's marketing-contact flag is read as the billing tier it is, never as consent on its own.

Questions buyers ask