Skip to main content

How to clone a HubSpot deal | DupliCat

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

This guide reflects current shipped behavior.

Cloning a deal is easy. Cloning a deal plus the right associations and line items is where assumptions break. This page covers the native baseline, then DupliCat’s explicit handling for repeatable deal clones.

DupliCat is a CleverCat operational utility for HubSpot for predictable duplication with clear boundaries.

Fast answer

Native HubSpot baseline (manual)

  • Open the deal record.
  • Use Actions -> Clone.
  • Review copied properties and association selections in the clone panel.
  • Fill required fields and any cleared unique values.
  • Save the cloned deal.
  • Reference: HubSpot Clone a record.

When native is enough

Native clone is often enough for occasional deal duplicates with minimal variability and light association requirements.

Where native breaks

  • Association expectations can vary across related object types.
  • Line items are records, not just fields — native clone may not handle them the way you expect.
  • Unique-field handling can force manual rework.
  • Repeated manual runs can drift from the intended template.

Operational utility path

Use DupliCat when deal clone behavior must stay consistent across repeated runs and operators.

Why this is harder than it sounds

  • Associations are not a single object graph — contacts, companies, line items, and other related records behave differently.
  • Deal line items are a separate record layer; if you only clone deal properties, you haven’t cloned the quote surface.
  • Multi-step copy expectations can drift across operators.
  • Manual clone review is fragile under high-throughput renewal workloads.
  • Workflow and card paths need consistent behavior to avoid revenue ops drift.

What you’ll get (DupliCat)

  • Deal cloning with templates/defaults (including portal and personal defaults).
  • Explicit association target selection per run.
  • “Copy associations” re-links selected associated records to the clone.
  • Deep line-item cloning: when line_items is selected for deals, DupliCat creates new line item records and associates them to the cloned deal.
  • Works from record-surface runs and from workflow runs (deepCloneLineItems).
  • Workflow action support when you need automation.

Prerequisites

  • DupliCat installed in your portal.
  • Agreement on which association types should be copied vs left alone.
  • A test deal with representative associations and line items.

Boundaries and limitations

Does

  • Clone deals with deterministic association selection.
  • Provide explicit deal line-item deep-clone behavior when enabled.
  • Keep association and line-item behavior explicit so operators can validate outcomes.

Does not

  • Deep-copy every association type by default.
  • Treat association copying as a substitute for portal-specific validation.
  • Replace rollout validation for your portal model.

Validation slice checklist (before rollout)

  • Pick a test deal with known associated records and a small set of line items.
  • Clone once with a minimal association set; verify links on the clone.
  • Clone again with the full association set you plan to use.
  • Enable deep line-item cloning and confirm:
    • The cloned deal has the expected line item count and values.
    • The line item records are new (IDs differ from the originals).
  • If you plan to automate: run the same config in a test workflow and verify outputs.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID + deal ID/URL.
  • Template selection + any overrides.
  • Association targets selected.
  • Whether line items were included / deep cloned (card or workflow).
  • Cloned deal ID/URL + original and cloned line item IDs (if available).
  • Screenshots of association sections.

Fallback: validate target behavior in a test slice, then use Known limitations and Support.

Next steps

FAQ

Does this clone contacts and companies linked to the deal?

Selected associations are re-linked to existing associated records. This is not the same as deep-copying every related record.

For deals, when line_items are selected, DupliCat creates new line item records and associates them to the clone.

Does HubSpot native clone handle all association types the same way?

Native clone behavior is documented by HubSpot and should be validated against your object setup: Clone a record.

Can I use templates for repeated deal clones?

Yes. DupliCat templates/defaults are designed for repeatable clone runs.

Does line-item deep clone work in workflows?

Yes. Workflow runs can use deepCloneLineItems controls in DupliCat workflow action configuration.

Can I run multiple duplicates in one pass?

Yes. DupliCat supports sequential duplicate runs (1-10) on supported card paths.

Are attachments and activities cloned?

DupliCat supports activity-record cloning and related-activity copying, but attachments are not cloned. If activity behavior matters for your deal process, validate that slice before rollout.

What should I verify after clone?

Verify key properties, association targets, line item count/amounts, and business-critical fields before wider rollout.