Executive summary
What it does, what it doesn't, and what to read next.
Use DupliCat when you need repeatable record clones in HubSpot and you want the rules written down once.
What changes
Before
Your team clones the same record types every week. Each run starts from scratch, someone cleans up the fields afterward, and the result depends on who did it. Associations get missed. The process isn't written down anywhere.
After
Configure a template once. Run it from the record card or a workflow trigger. Field verification starts from HubSpot property history, not memory. Every team member gets the same result.
Free evaluation tier available. Install and validate one controlled clone before broader rollout.
Install free in HubSpot → Read setup docs →Quick spec
Concrete scope before deeper docs.
Fit check
Use this before you install.
Support hours: Monday-Friday, 9:00 AM to 5:00 PM America/Los_Angeles.
Response target: General support first response target: within 1 business day.
Visual proof
A flow diagram plus real card captures, mapped to shipped behavior.
Walkthrough video coming soon. In the meantime, install the free tier and try it in your own portal. Install free →
Shipped behavior
Copy below sticks to shipped behavior and documented boundaries.
Use DupliCat for repeatable cloning across deals, contacts, companies, tickets, orders, projects, quotes, notes, tasks, calls, meetings, emails, and custom objects.
Set `Number of duplicates` (`1-10`) per run. When count > 1, DupliCat applies numbered naming with a `[Duplicate]` name prefix so records are distinguishable.
Copies writable properties. By default it copies populated (non-empty) values; you can enable empty-property copying when needed.
Optionally re-links selected associations. For deals, line items can be deep-cloned (new line item records) instead of linked.
Clone notes, tasks, calls, meetings, and emails when those records are part of the workflow you are standardizing.
DupliCat does not provide a separate per-run customer-facing audit trail. CleverCat retains minimal operation records for support and operational review. Those records exclude property names and property values. For record-level verification, use HubSpot property history and the record activity timeline.
Settings and templates control naming, association copying, and deal line-item handling for repeatable operator runs.
Save named templates per object type, set portal and personal defaults, and pick a template per clone run.
Templates support date shift, owner rules, and pipeline/stage mapping (for deals and tickets) for advanced repeatable cloning behavior.
Start with HubSpot property history. If you need help, include portal ID, timestamp/timezone, and any visible warning/error text (plus workflow request ID if used).
Operator flow
Use a narrow first-run path before wider adoption.
Install + authorize
Install in HubSpot, complete authorization, and confirm you can access settings.
Set defaults + templates
Configure portal defaults, then save templates for your first object type. Optionally set portal and personal defaults.
Configure entry paths
Add DupliCat to the record views your team uses and, if needed, configure the workflow action with template and override inputs.
Validate once
Run a small test clone, validate prefix naming behavior, duplicate count outcomes, template loading, and HubSpot Property history.
Scale deliberately
Review workflow docs, known limits, and release notes before expanding access to your full team.
Use cases
Examples map to repeatable operator tickets rather than generic feature bullets.
Clone each renewal deal from a vetted template with line items and keep naming/rules consistent across the batch.
Clone company/contact/ticket records for a new region while preserving the associations you intentionally copy.
Run DupliCat from workflow automation when an approval stage is met, then review workflow history outputs before scaling.
Use enhanced overrides (date shift, owner rules, pipeline/stage mapping) so recurring setup stays repeatable.
Common problems
Problem phrasing teams use before they evaluate setup details.
Scope boundaries
Boundaries are part of the product: clear scope, clear fallbacks.
Duplicate core CRM records
DupliCat supports deals, contacts, companies, tickets, orders, projects, quotes, notes, tasks, calls, meetings, emails, and custom objects.
Run where your team already works
Use DupliCat in HubSpot record views today, and use the workflow action when you want repeatable automation for contacts, companies, deals, tickets, orders, or projects.
Deep-clone deal line items
When `line_items` is selected for deals, new line item records are created and re-associated to the clone.
Clone activity objects and related activities
Notes, tasks, calls, meetings, and emails are supported when those records or related activities are part of the process you are standardizing.
Apply portal and personal defaults
Templates and defaults exist at both scopes to keep team runs consistent while allowing user-level control.
Copy read-only/system-managed fields
Why: DupliCat copies writable properties only. Fallback: review critical fields after each run and handle system fields manually.
Deep-clone every associated record
Why: associations are re-linked; deep duplication is scoped. Fallback: deep-clone deal line items when needed, and otherwise relink or recreate associations intentionally.
Clone attachments
Why: attachments remain out of scope. Fallback: re-attach required files manually after clone.
Provide a separate audit trail
Why: DupliCat does not provide a separate per-run customer-facing audit trail. Fallback: For record-level verification, use HubSpot property history and the record activity timeline.
Availability and pricing
Pricing is published, and setup has a controlled first-run path.
Docs and trust
Everything needed to evaluate and operate DupliCat.
Install, connect OAuth, configure defaults/templates, and run your first validated clone.
Set up and operate the workflow action, including configuration and run outcomes.
Guides
Problem-first guides that route to setup, limits, and pricing.
Deal association handling plus line-item deep-clone behavior in current release.
FAQ
Operational answers linked to setup, scope, and boundary docs.
Need help evaluating? Ask a rollout question →
