Skip to main content

How to clone a HubSpot record | DupliCat

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

This guide reflects current shipped behavior.

HubSpot has a native clone action. It works for the occasional one-off. The operational problem is consistency: when clone becomes “a process,” manual choices start to drift.

DupliCat is a CleverCat operational utility for HubSpot for predictable record duplication (templates, defaults, and a workflow action when you need automation).

Fast answer

Native HubSpot baseline (manual)

  • Open the source record, then use Actions -> Clone.
  • Review copied values and associations in the clone panel.
  • Fill required values and any cleared unique values before save.
  • Create the cloned record.
  • Reference: HubSpot Clone a record.

When native is enough

Native clone is usually enough for occasional one-off duplication tasks with light association requirements.

Where native breaks

  • Unique fields (for example email/domain) are cleared and need manual handling.
  • Native clone does not necessarily include every related artifact; validate your expectations against HubSpot docs for your portal.
  • Repeated manual clone runs can drift across operators.

Operational utility path

Use DupliCat when you need repeatable duplication rules (templates/defaults), optional association handling, configured preview-card support, and a workflow action for controlled automation.

Why this is harder than it sounds

  • Associations are not one thing: contacts, companies, line items, and other related records behave differently.
  • Unique constraints can create hidden post-clone cleanup work.
  • Manual rebuilds and one-off clone choices introduce operational drift.
  • Workflow automation often needs more than simple record creation.

What you’ll get (DupliCat)

  • Supports deals, contacts, companies, tickets, orders, projects, quotes, notes, tasks, calls, meetings, emails, and custom objects.
  • Copies writable properties (non-empty by default; can include empty properties when enabled).
  • Optional association copying (re-link selected association types to the clone).
  • For Deals: optional deep duplicate line items (creates new line item records).
  • Supports 1-10 duplicates per run.
  • Supports enhanced overrides such as date shift, owner rules, and pipeline/stage mapping when configured.
  • Multi-duplicate card runs use a [Duplicate] name prefix so cloned records stay distinguishable.
  • Workflow action: DupliCat: Clone through workflow.

Prerequisites

  • DupliCat installed in your HubSpot portal.
  • If you plan to use workflow cloning: access to HubSpot Workflows for the object type you’re cloning.
  • A test record (or sandbox) for first-run validation.

Boundaries and limitations

Does

  • Make duplication behavior template-driven and repeatable.
  • Keep duplicate behavior explicit so operators are not guessing.

Does not

  • Guarantee your portal’s required/unique field rules are satisfied automatically.
  • Replace test-slice validation before broader rollout.

Validation slice checklist (before rollout)

  • Pick one object type and one test record with representative associations.
  • Run 1 duplicate with defaults; verify required/unique fields and association links.
  • Create a template and run the same clone again; confirm outcomes match.
  • If duplicating Deals with line items: enable deep line items and confirm new line item records exist on the clone.
  • If you plan to run batches, test 2–3 duplicates before using 10.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID.
  • Object type + source record ID/URL.
  • Run path (card vs workflow) + number of duplicates.
  • Template selection (portal/personal default or explicit template) and any overrides used.
  • Association targets selected + whether deepCloneLineItems was enabled (Deals only).
  • Cloned record ID(s)/URL(s) + any request ID/error shown.

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

Next steps

FAQ

No. Native clone has limits. For known native behavior, use HubSpot’s Clone a record.

Why are email or domain values blank after clone?

Unique values can be cleared in native clone paths to avoid uniqueness conflicts.

Can DupliCat clone quotes, activity records, and custom objects?

Yes. DupliCat supports quotes, notes, tasks, calls, meetings, emails, and custom objects. Validate your exact setup in a test slice before wider rollout.

Can I run clone logic in workflows?

Yes. DupliCat includes a workflow action entry path.

Where should I verify field-level clone outcomes?

Use HubSpot Property history on the cloned record, then escalate with request context if needed.