Real estate CRM contact merges should begin with evidence that two records describe the same person. A shared name or address is a reason to investigate; spouses and joint buyers need a separate decision about how their profiles should relate. Once identity is settled, review source attribution, activity history, communication preferences, and automations individually. What survives depends on the product, chosen primary record, and account settings.

This checklist is for brokerage administrators and agents reviewing individual contacts or preparing a larger cleanup. Product examples reflect vendor documentation dated before October 3, 2026; check which features and settings apply to your account. Establish recovery limits before approving a merge.

1. Establish identity before choosing a primary record

Compare the original inquiries, conversations, and contact details for each proposed pair. Look for an explicit connection: the person confirmed a new email address, an agent documented a name change, or the conversation clearly continues an earlier inquiry. A matching phone number or email warrants review but should not settle the decision alone.

Use three outcomes:

• Confirmed duplicate: Both records describe one person. Document the evidence and proceed to field review.
• Related people: Keep each person's identity clear. Decide whether separate profiles or a supported relationship feature better fits their follow-up needs.
• Unresolved: Leave the records separate and assign someone to investigate.

For example, two buyers sharing a surname and home address should not pass your duplicate test on those facts alone. Conversely, a returning client using a different email may belong on the same person record while retaining separate purchase and sale opportunities.

Follow Up Boss illustrates the household trade-off. Its Contact Relationships documentation describes combining related people's communications on one profile, but says automated emails can target only the primary contact. Consider that limitation before choosing the arrangement for people who need individual follow-up.

2. Preserve the evidence and intended outcome

Make merge approval part of your agent business systems: assign an administrator to approve the operation and the responsible agent to resolve identity or ownership questions. Assemble a review packet containing:

• Both record IDs, profile links, names, email addresses, phone numbers, and assigned agents.
• Original and latest source values, campaign or referral details, inquiry dates, and associated opportunities.
• Notes, messages, appointments, tasks, attachments, and other history relevant to the relationship.
• Communication restrictions and the evidence behind them, including dates and affected addresses or numbers.
• Active automations, pending steps, and connections to other systems.

Open the saved material and check what it contains. Anything needed for review but absent from an export needs another preservation method. Our CRM export checklist provides a broader inventory for preserving records before a major data change.

Record the intended outcome alongside the evidence: which profile is primary, which conflicting values should remain, and why. A cleaner-looking name is not enough reason to choose the primary record.

3. Separate field survival from lead attribution after merge

A surviving source field and a complete account of how a client arrived serve different purposes. Compare the documented merge rules with the information your brokerage needs.

These examples do not establish what another CRM preserves. For your system, review source, owner, stage, custom fields, and activity history separately.

Consider a hypothetical client who first attended an open house and later submitted a portal inquiry. If your report groups contacts by the surviving source field, check how that field will represent the two events. Preserve both inquiry dates and sources separately from the chosen reporting category.

Before merging, decide whether a report is meant to count people, inquiries, opportunities, or closings. Afterward, reconcile a sample against that definition. Do not use whichever source happens to survive as the sole evidence for referral credit or an agent-assignment dispute.

4. Resolve communication preferences by recipient and channel

For each email address and phone number, record the relevant preference, its date, its scope, and the supporting message or form submission. Keep email, text, and calling restrictions distinguishable. Also distinguish an instruction from the person from an administrative field change.

HubSpot's messaging-subscription documentation says email subscription preferences belong to the email address rather than the contact record. Check every affected address when a proposed merge involves multiple emails.

When preferences conflict, hold the affected marketing while the conflict is reviewed. Preserve the restriction and its evidence; do not interpret a blank field as permission or transfer one spouse's preference to the other. Review the wording and purpose of a newly submitted property inquiry before deciding whether it changes an earlier restriction.

After the merge, inspect both the CRM preference display and the settings used by the connected sending service before resuming marketing. Ask brokerage counsel to resolve unclear consent or jurisdiction-specific requirements.

5. Check scheduled work and new enrollment separately

A merge review needs to address both work already scheduled and the resulting record's eligibility for new work.

In Follow Up Boss, the main contact's running action plan continues, while the other merged contacts' action plans pause.

For workflow-enabled HubSpot accounts, the Primary ID Preservation for Merged Records beta keeps the primary record enrolled and unenrolls the secondary. Outside that beta, both records leave active workflows.

New enrollment is a separate consideration. HubSpot's workflow enrollment settings allow enrollment when a merged contact meets the conditions; that option is off by default. Later re-enrollment requires re-enrollment to be enabled and the contact to meet its triggers again. When enrolled, a merged contact starts at the beginning of the workflow.

Before changing client records, test representative cases with synthetic contacts and outbound delivery disabled. Include conflicting source values, different stages, an opt-out, and a pending follow-up. Check recipient addresses, message personalization, agent routing, and scheduled actions. Include connected marketing tools in this real estate software operations review.

If you cannot test a consequential behavior, obtain account-specific confirmation from the vendor before approving that merge.

6. Establish recovery limits, then verify the result

HubSpot says records cannot be unmerged. Follow Up Boss likewise says the operation cannot be undone: separating someone requires a new contact, and past conversations do not transfer to that new profile.

Ask what reconstruction would require before proceeding. A saved spreadsheet is not proof that every relationship, message, or pending action can be restored.

Begin with a small batch, then check these completion criteria before approving further merges:

• The resulting profile represents the intended person or deliberately chosen relationship arrangement.
• Source values, ownership, opportunities, and important history match the documented decision.
• Communication restrictions remain correct for each recipient and channel.
• Automations and connected services show the intended recipients and next actions.
• The review packet records the old and resulting IDs, operator, date, and unresolved exceptions.

Assign unresolved exceptions to a reviewer and keep those contacts out of the next batch until the questions are settled.