Records, imports, and enrichment

Create a record manually

Open CRM → Leads, People, or Companies, choose the create action, and enter the minimum trustworthy identity. Search first using email, phone, name, company, or another stable identifier. Add an owner and lifecycle state only when the team can act on them.

Open a record to review its details and related activity. Depending on record type and workspace features, the detail view can surface notes, tasks, conversations, associated records, enrichment, and other operational history.

Understand identity

Email addresses and phone numbers are useful identifiers but can be shared, changed, or formatted differently. Company names and domains can also vary. Use normalization and the duplicate review tools presented by the product; do not merge records solely because names look similar.

Prepare an import

1. Export a backup from the source system.
2. Remove unnecessary columns and clearly label the header row.
3. Normalize dates, countries, phone formats, email values, owners, and lifecycle labels.
4. Preserve source, consent, suppression, and acquisition dates.
5. Decide how the file should match existing records and what should happen on a conflict.
6. Create required custom fields before mapping.
7. Test with a small representative file.

During field mapping, inspect every low-confidence or guessed match. Map identifiers and consent fields manually. A successful upload only confirms processing; validate actual records, ownership, associations, and duplicates afterward.

Work with duplicates

Use the duplicate-review experience where available. Choose the survivor based on the most reliable identity and history. Before merging or deleting anything, compare ownership, consent, activity, company relationships, deal associations, tasks, and custom fields. Keep an audit note when the decision matters operationally.

Use enrichment

Enrichment can propose or add details for a lead, person, or company. Availability and usage cost can depend on plan and provider. Before running it:

• Confirm the record is the intended person or business.
• Understand which fields may be written and whether existing values can change.
• Select only records for which enrichment is appropriate.
• Review usage estimates or limits presented by Spacebrain.

After enrichment, verify important facts against an owned or authoritative source. Enriched data can be outdated or refer to a similarly named entity. Never treat a generated or third-party field as proof of consent.

Export and cleanup

Apply the intended view and filters before exporting, verify the row count, and protect the downloaded file as customer data. Bulk edits and deletes should start with a narrow selection and a second review of workspace, record type, and count.