Skip to main content

How to clone a HubSpot company | DupliCat

Last updated: March 23, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

Company cloning in HubSpot is common in account-based workflows: new regions, franchise locations, partner onboarding, and event venue setups all benefit from a clean source record to clone from. The native clone covers the basics. The operational problem appears at volume and on repeat.

DupliCat is a CleverCat operational utility for HubSpot for predictable record duplication with templates, defaults, and documented boundaries.

Fast answer

Native HubSpot baseline (manual)

  • Open the source company record.
  • Use Actions -> Clone.
  • Review copied properties in the clone panel.
  • Fill required values and unique fields before saving.
  • Reference: HubSpot Clone a record.

When native is enough

Native clone covers occasional company duplicates where association requirements are simple and one-off field cleanup is acceptable.

Where native breaks

  • Domain fields and other unique properties are cleared and require manual handling every time.
  • Repeated manual clone runs across operators produce inconsistent outputs.
  • Association handling — linked contacts, deals, and tickets — isn’t always predictable without a configured template.
  • No save-and-reuse layer means each run is a fresh decision rather than a repeatable process.

Operational utility path

Use DupliCat when company cloning happens on a schedule, across multiple operators, or as part of an automated onboarding or account expansion workflow.

Why this is harder than it sounds

  • Domain and website URL fields are unique constraints: cleared on clone and require manual fill-in to avoid conflicts.
  • Account-based models often carry deep association graphs: contacts, deals, tickets, and related records. Which ones clone and which don’t matters.
  • Template-less cloning drifts across operators: one person copies the industry field, another doesn’t, and the data model slowly becomes inconsistent.
  • Automated onboarding workflows that trigger company creation need deterministic behavior, not manual interpretation.

What you’ll get (DupliCat)

  • Company cloning with templates and portal/personal defaults.
  • Configurable association copying: re-link contacts, deals, tickets, and other supported association types to the clone.
  • Explicit property copying: non-empty by default; optionally include empty properties.
  • 1-10 sequential duplicates per card run.
  • Workflow action: DupliCat: Clone through workflow — automate company clone logic from HubSpot Workflows.
  • [Duplicate] name prefix on multi-duplicate runs for easy identification.

Prerequisites

  • DupliCat installed in your HubSpot portal.
  • A test company record with representative associations for first-run validation.
  • Agreement on which association types (contacts, deals, tickets) should carry over.
  • If using workflow automation: access to HubSpot Workflows for Companies.

Boundaries and limitations

Does

  • Make company duplication template-driven and repeatable across operators.
  • Keep field and association behavior explicit so clones are predictable.
  • Support workflow-entry automation for scaled company clone logic.

Does not

  • Automatically fill in unique fields (domain, website) after clone.
  • Deep-copy every related contact or deal — association re-linking references existing records, not new copies.
  • Replace test-slice validation before broader rollout.

Validation slice checklist (before rollout)

  • Pick one test company with known associated contacts and deals.
  • Clone once with defaults; verify which properties carried over and check unique fields.
  • Create a template with your intended defaults; run the same clone and confirm consistent output.
  • Verify association links on the cloned company record.
  • If automating: run a test workflow on a single company and confirm clone outputs match expectations.
  • Test 2–3 duplicates in a batch before scaling to 10.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID.
  • Company ID/URL of the source record.
  • Run path (card vs workflow) and number of duplicates.
  • Template selection (portal/personal default or explicit template) and overrides used.
  • Association targets selected.
  • Cloned record ID(s)/URL(s) and any error message or request ID shown.

Fallback: use Known limitations and Support with portal-specific context before broad rollout.

Next steps

FAQ

Does cloning a company copy its associated contacts?

Association re-linking references existing associated records — it doesn’t create new contact records. You control which association types carry over per run.

Are domain or website fields copied to the clone?

HubSpot treats domain as a unique constraint and may clear it on clone. Handle unique fields manually after each clone run.

Can I save a template so every company clone has the same defaults?

Yes. DupliCat templates save your field defaults, association settings, and overrides so every run produces consistent output regardless of which operator initiates it.

Can I clone companies automatically from a HubSpot workflow?

Yes. DupliCat includes a Clone through workflow action that works with HubSpot Company Workflows.

How many companies can I clone in a single run?

DupliCat supports 1-10 sequential duplicates per card run on supported object types.

HubSpot does a lot. Why add DupliCat for company cloning?

HubSpot does a lot. For everything else — template-driven, repeatable company cloning with controlled association handling — there’s CleverCat.