A website enquiry reaches HubSpot with the right name and email address, but the contact appears under the wrong company. Before your team sends a proposal or starts follow-up, establish which relationship is wrong and how it was created.
Start with one affected contact. Compare the company name stored on that contact, its associated company records and the company marked Primary. Then inspect the history, correct the responsible form or matching rule, and repair the existing relationship.
Check which company information is wrong
HubSpot has several places where a company can appear. They serve different purposes:
- The contact’s Company name property: text stored on the person’s record.
- Associated companies: the company records linked to that contact.
- The primary company: the linked company carrying the Primary label.
HubSpot’s contact property reference confirms that the contact’s Company name is separate from the associated company’s name. Automatic or manual association does not update that contact property. Changing the text therefore does not repair an incorrect link.
Open the linked company itself and check its identity. A familiar display name is not enough: compare the domain, the original enquiry and what your team knows about the customer. Record the contact and company IDs so everyone investigating uses the same records.
Consider a consultant requesting a quote for a client. Their employer, the organisation buying the work and the company named in the enquiry may differ legitimately. Agree what each relationship should represent before changing it.
Find when the relationship changed
In the contact record’s Actions menu, open View association history. HubSpot’s association guidance explains how to inspect relationship changes, their source and date. Compare the relevant event with the enquiry, import or integration run.
Separately, use property history to inspect earlier values and the source and time of changes to Email, Company name and the company’s domain. The history of a field and the history of a relationship answer different questions.
Build a short timeline: what arrived from the website, which company was linked, and what changed afterwards. If the relationship was correct initially, investigate the later operation. Ask your administrator to inspect the relevant workflow, import mapping or integration record rather than assuming the website caused it.
If names or email addresses belonging to different people have also been combined, use our separate guide to HubSpot forms overwriting contacts. Establish the correct person before repairing their business relationships.
Check whether email-domain matching can identify the right company
HubSpot’s automatic company association matches the contact’s email domain with Company domain name. Its documented behaviour includes these limits:
- If several company records share that domain, you cannot select which one this automatic matching uses.
- An existing association to a different domain is not overridden by this setting.
This makes domain matching worth reviewing for groups with several trading companies, franchises or contacts who represent other organisations. An email domain alone may not distinguish the business buying your service.
For example, imagine two separate companies in a group whose staff share one email domain. Decide whether your CRM should represent the group, each trading company or both. Ask your administrator to implement an explicit selection or review process where the domain cannot resolve that choice.
Domain exclusions can limit automatic matching in most scenarios. Turning the setting off leaves existing records unchanged. Treat either change as control of future behaviour, followed by a separate review of affected contacts.
Inspect company fields in the website form
Check which object each form field updates. A field labelled “Company” could populate the contact’s Company name or a property on a company record. Include hidden fields and mappings applied by the website integration.
HubSpot’s automatic-association guidance states that forms submitting company properties can associate the contact with the submitted company regardless of the automatic-association setting or domain exclusions. That exception matters if you switched the setting off but the same problem continues.
HubSpot’s deduplication documentation adds a separate consideration: company properties submitted with Company domain name update the matching company or create one if no domain matches. Without a submitted domain, the contact’s primary company can be updated where applicable.
Ask what the visitor’s answer means. Is “Company” their employer or the client requesting the work? Map the answer deliberately. Avoid sending information about a project’s end customer into an existing employer record simply because both are called company details.
If an integration creates company records through the API, the same documentation says they are not deduplicated by Company domain name. Have the developer check its matching logic before assuming repeated domains will be handled automatically.
Repair the association and choose the primary company
Once the intended relationship is confirmed, work through a small sample with your CRM administrator:
- Open the contact’s company association card and add the correct existing company if it is missing.
- Use Set as primary on the appropriate company.
- Remove any incorrect association separately. Replacing the primary company leaves the previous company associated.
- Recheck the record from both the contact and company sides.
HubSpot supports contacts associated with multiple companies. Its primary relationship can be referenced in segments, workflows, reports and personalisation. Decide which company should drive those uses; keep other relationships only where they remain meaningful.
Avoid merging distinct companies merely to make an ambiguous email domain match. Likewise, avoid deleting a valid company record to fix one contact’s link. First correct the relationship, then investigate any genuine duplicate records as a separate cleanup.
Check where calls, emails and meetings are logged
A correct company link does not finish the investigation if sales activity still appears under the wrong business. HubSpot’s activity-association settings depend on the activity type, where it was logged and the records involved. Available rules include logging to the primary company, all associated records or recent associations.
The same guidance distinguishes custom rules for activities created or logged within HubSpot from eligible activities created by HubSpot-built integrations, which follow default behaviour. Shared-inbox email routes also have separate rules. Test the route your team actually uses.
Review an affected call or meeting individually. Do not assume changing a contact’s primary company has repaired every historical activity. Check open opportunities and any proposal awaiting a response, then give the salesperson the corrected customer context.
Test the complete enquiry route before bulk cleanup
Use controlled test contacts and company records, keeping automated customer messages out of the test. Agree the expected relationship before submitting each enquiry.
- A new business contact: does the enquiry reach the intended company without creating an unnecessary record?
- A returning contact: does a new request preserve the intended relationship?
- A shared-domain example: can the process distinguish the relevant trading company?
- A representative acting for a client: are employer and buying organisation kept clear?
- The normal sales handover: does a logged call or meeting appear on the intended records?
Keep the submission time and resulting record IDs. Recheck after the next relevant workflow or integration run. A manual correction that is later replaced has not resolved the underlying cause.
For existing records, prioritise active enquiries, open deals and upcoming meetings. Confirm the right company with the responsible salesperson, record the agreed correction and review a small batch before extending it. Check any affected reports and automated follow-up as part of that review.
If your website and CRM disagree about who an enquiry belongs to, talk to BuzzBoost about the enquiry journey. We can help you work through the form, integration and sales handover so your team has the right context when it responds.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
