GoHighLevel duplicate-contact settings affect how some new submissions match existing people. They do not answer whether two sales enquiries should become one opportunity. Keep those decisions separate when connecting forms, imports and external lead sources.

Check the submission source first

HighLevel’s Contact Deduplication Preferences guide distinguishes Forms and Zapier from CSV imports. It documents primary and optional secondary matching fields and says CSV imports use their own matching behaviour rather than simply following the duplicate-contact toggle.

That distinction explains why changing one setting may not produce the same result across all channels. Write a source inventory: website form, imported list, integration and social message. Record the identifiers each supplies and the resulting contact ID.

Define when two records represent the same person

Use realistic examples before selecting a matching field. A person may use a personal address on one form and a work address on another. Two family members may share a phone number. A business may have multiple people behind a general email address.

ExampleDecision to review
Same email, corrected phoneUpdate the known person or review conflicting details
Shared phone, different namesAvoid merging solely because the number matches
New source for an existing contactPreserve useful attribution without duplicating the person
Two jobs for one personKeep the person linked to distinct pieces of sales work

Test a form and a CSV as separate operations

Use a small internal sample and export the existing contact references before testing. Submit a form with a changed detail, then run the corresponding controlled import. Inspect the exact result after each step; do not assume the CSV repeats the form’s behaviour.

For each example, record the source identifier, matched contact ID, fields changed and any information overwritten. Review ambiguous matches with the office staff who know what the record means. A smaller contact count is not proof that the merges were correct.

Keep opportunity duplication independent

HighLevel’s Create Opportunity guide describes its duplicate logic using contact ID. A contact can be correctly matched while the sales process still requires a second opportunity for another property, project or request.

Write the business policy explicitly: for example, a repeat form for the same estimate updates the open request, while an enquiry for another site receives its own review. Implement that policy with the available fields and workflow actions rather than relying on contact matching to infer job identity.

Review what happens after a merge

Check ownership, conversation history, communication preferences and active follow-ups. A newly consolidated contact might otherwise remain in overlapping outreach paths. Keep a correction route for staff and retain the source references needed to investigate an incorrect match.

Measure incorrect merges, duplicate contacts needing manual review and duplicate opportunities separately. The useful result is an intelligible customer record with the right work attached, not the lowest possible number of records in the CRM.

Designing a Contact Matching Policy Before Touching Any Settings

Before adjusting any field in a CRM platform, a business benefits from writing down its own rules for what makes two records the same person. That document becomes the acceptance standard against which any system behaviour is evaluated. Without it, a team ends up reverse-engineering policy from whatever the software happened to do, which produces inconsistent outcomes and makes future troubleshooting harder.

A matching policy should distinguish between three separate questions: whether two submissions describe the same individual, whether that individual has the same relationship to the business as before, and whether the work attached to the submission belongs on an existing record or a new one. Conflating these questions is where most contact-management problems originate, because a CRM field called "match on email" answers only the first question and says nothing useful about the second or third.

Write the policy in plain language before translating it into system configuration. For a service business taking enquiries by form, an illustrative policy statement might read: a person is treated as the same contact when the submitted email address exactly matches a stored address; if only a phone number matches and the name differs materially, the record is held for manual review rather than merged automatically; if a known contact submits a form for a new service address, the contact record is updated but a new piece of work is opened rather than an existing one reopened. Each sentence in a policy like that corresponds to a distinct configuration or workflow decision. Reviewing them one at a time prevents settings from conflicting with each other.

Mapping Identifiers by Source Before Configuring Matching

Different submission channels supply different identifiers with different reliability. A website enquiry form typically captures whatever the visitor types, which means an email address may be misspelled or a phone number may omit a country code. A CSV import prepared from an existing customer database may carry a unique account number that the CRM field set does not include by default. An integration from a third-party booking tool may send a contact with a phone number but no email at all.

A source inventory is a practical tool for surfacing these differences before they cause problems. For each channel that feeds contacts into the system, record the fields it reliably supplies, the fields it sometimes omits, the format each field arrives in, and whether the source assigns any identifier of its own that could be stored as a reference. A simple internal table with one row per source and columns for those four questions takes little time to prepare and becomes the reference document when a merge produces an unexpected result.

The inventory also reveals where matching will be structurally unreliable regardless of settings. If a social messaging channel supplies only a name, no email field matching will help because the identifier is absent. If a phone-based booking line creates records using a staff-entered name and a caller-supplied number, the risk of family members sharing a number creating a merged record becomes visible before it happens rather than after. Identifying these gaps in advance allows a business to decide on a channel-specific handling rule, such as routing all records from that source to a review queue rather than allowing automatic matching.

A Worked Scenario: A Recurring Enquiry From an Existing Contact

Consider a fictional residential services business. A contact named Marcus Webb submitted a form enquiry for a property assessment and was added to the CRM with his personal email address. Several months later, a form submission arrives using the same email address but listing a different property address and a mobile number that does not match the stored one.

Without a written policy, a staff member reviewing the CRM might merge the records immediately because the email matches, overwriting the old phone number with the new one and closing the attribution trail for the original enquiry source. Alternatively, a different staff member might create a second contact record to preserve the original details, producing a genuine duplicate.

With a policy in place, the handling is deterministic. The email match identifies the same person. The different property address indicates a new piece of work rather than a correction to an existing one. The phone number difference is flagged for the contact owner to resolve, because it could represent a new number, a second household member using the same email, or a data entry error. The system creates or updates the contact record according to the match, opens a new work item for the new address, and the contact owner receives a task to confirm or correct the phone field before the next outreach step runs.

This scenario is illustrative, but the decisions it contains are real ones any service business faces. The value of writing the policy first is that the same reasoning applies consistently whether the submission arrives by form, by import, or through an integration, and a new staff member can follow the same steps without having to infer intent from the configuration.

Preparing and Reviewing a Controlled Import

A CSV import requires its own preparation steps that differ from form submission testing. Before running any import against a live contact database, a business should export a snapshot of the existing records that are likely to be affected and store it somewhere accessible. That snapshot is the baseline for verifying what changed, correcting errors, and recovering from an unintended merge.

Prepare the import file in a staged way rather than loading everything at once. Begin with a small group of records that includes deliberate test cases: a record with an email address that matches an existing contact exactly, a record with a phone number that matches but a different email, a record with no shared identifier with any existing contact, and a record with a name that is similar but not identical to an existing contact name. After running the import, review each case individually and record the outcome against the expected outcome from the matching policy.

Particular attention is worth giving to fields that can be overwritten during an import match. If an existing contact has a manually corrected phone number and the import file contains the original uncorrected version, a match on email could silently restore the incorrect value. Identifying which fields are updated on a match and which are preserved requires checking the actual result in each test case, not assuming the platform will protect manually edited values. Where the behaviour does not match the business need, the solution may be to remove that column from the import file, to add a custom field for the imported value, or to process the update through a different step after the import completes.

Ownership and Follow-Up After a Contact Is Consolidated

When two records are merged or when an import updates an existing contact, the resulting record inherits a history that may have come from more than one source. Staff who were working from either of the original records need to know that the consolidation happened and understand what the combined record now contains. Without a notification or review step, it is possible for a team member to continue working from a cached or printed version of the old record, or to send a follow-up that duplicates one already sent from the merged record's history.

Ownership assignment deserves explicit attention. If the two records being consolidated were owned by different staff members, the merged record will have one owner and one of those staff members will lose visibility unless a sharing or notification arrangement is in place. A useful business question to answer in advance is: when a contact is merged, who is notified, who reviews the combined record, and within what timeframe is the ownership question resolved? Answering that question in the matching policy rather than leaving it to ad-hoc judgment reduces the chance that a consolidated contact receives no follow-up because both original owners assumed the other was handling it.

Communication preferences and opt-out status also require review after consolidation. If one record carried a suppression from a previous unsubscribe and the merged record does not carry that suppression forward, an outreach step could reach someone who had previously opted out. This is an area where human review of the merged record is appropriate before any automated communication sequence continues, rather than relying on the merge process alone to resolve it correctly.

Distinguishing Contact Duplication From Opportunity Duplication in Practice

A practical acceptance exercise for any contact-matching configuration should include at least one scenario where the contact record should be consolidated but the work attached to it should not be. This tests whether the team's policy and the system's behaviour agree on the boundary between person-identity and work-identity.

In a fictional scenario, a property management company submits enquiries on behalf of multiple landlords using a single company email address. The contact matching logic may correctly identify all submissions as belonging to the same contact record because the email address is consistent. The business, however, needs each property to be tracked as a separate piece of work with its own status, notes, and owner. If the system or the team treats the contact match as a reason to consolidate all the work onto a single record, the pipeline becomes unmanageable and attribution is lost.

The acceptance exercise should include a checklist of observable evidence rather than a subjective impression of whether things look right. Observable items might include: the contact record shows a single entry for the organisation, each piece of work appears as a distinct item with its own status field populated, the contact owner can view all associated work from the contact record, and a staff member assigned to one piece of work cannot accidentally modify a different piece of work while updating their own. If any of those items cannot be confirmed by direct inspection of the record, the configuration or the workflow logic requires adjustment before the channel goes live.

Exception Handling and Correction Routes for Staff

Even a well-designed matching policy will produce incorrect results in some cases, because data quality at the point of entry is outside the business's full control. A visitor may mistype an email address in a way that happens to match another contact's address. A list supplier may have assigned the same phone number to two different records. A staff member entering a walk-in enquiry may use a generic placeholder email that a previous enquiry also used.

Having a defined correction route matters as much as the initial matching logic. Staff should know how to flag a suspected incorrect merge, where to record the original source references so the investigation has a starting point, who is responsible for reviewing and correcting the record, and how to verify that any outreach already sent from the incorrect merged record has been accounted for. Without these steps, an error discovered after the fact becomes difficult to unwind because the history of what was sent and to whom is ambiguous.

A practical measure is to retain the source submission reference on every contact record as a custom field, even when the contact is matched to an existing record rather than created fresh. That reference allows a staff member to return to the original submission and compare it against the current record if a discrepancy is noticed later. It also supports a periodic quality review where a sample of recent matches is inspected to confirm that the policy is producing the intended results, rather than waiting for a visible problem to prompt investigation.

Questions That Should Change a Purchase or Configuration Decision

When evaluating contact-matching behaviour as part of a broader CRM decision, a business benefits from asking questions that reveal how the system handles its specific data patterns rather than questions that invite a general feature confirmation. Useful questions to bring to any demonstration or evaluation include: what happens to a field value on an existing record when an import match overwrites it, and can that behaviour be controlled at the field level rather than globally; how does the system behave when a submission matches on one field but conflicts on another, and does it merge, hold, or create; what record is created when no match is found and the submission contains only a partial set of fields; and how is a merge reversed if it is found to be incorrect after outreach has already been sent from the consolidated record.

The answers to these questions, tested against the business's own sample data rather than a vendor-supplied demonstration dataset, reveal whether the system's default behaviour aligns with the business's written policy or requires workflow customisation to bridge the gap. That gap assessment is a practical decision input: a business that needs extensive custom logic to make basic matching work correctly should weigh that implementation cost against alternatives, while a business whose policy maps closely to the platform's defaults faces a simpler setup task. Neither outcome is inherently better; the value is in knowing which situation applies before committing to a configuration approach.

Returning to the source inventory and the written matching policy at each stage of setup and testing keeps the evaluation grounded in observable, business-specific outcomes rather than general platform capability. A contact record that accurately reflects a single identifiable person, with the right work attached and the right staff responsible for it, is the concrete result worth measuring against.

Related guides

Comparing business systems? Explore Sysevo CRM or book a Sysevo demo against the same requirements. This is an independent Sysevo editorial guide based on the linked vendor documentation, reviewed 2 November 2026. Examples are illustrative; no hands-on vendor test or guaranteed result is claimed. Sysevo publishes this guide and sells its own software.

For current Sysevo subscriptions and usage options, compare plans and pricing.

Related trade guide

GoHighLevel for Pest Control: New Leads and Repeat Visits