DupliCat Known Limitations (v1)

This page documents current DupliCat v1 boundaries to reduce rollout surprises and support churn.

These limits are intentional for predictable operator behavior.

Boundaries (quick read)

DupliCat does:

Duplicate Deals, Contacts, Companies, Tickets, Orders, Projects, Quotes, and Custom Objects.
Support broad DupliCat capability claims while keeping current card surfaces explicit (sidebar/preview when configured) and workflow cloning optional.
Support Number of duplicates (1-10) per card execution.
Re-link selected associations; deep-clone deal line_items when selected.
Copy related activities (notes, tasks, calls, meetings, emails) from the source record when selected.

DupliCat does not:

Clone attachments.
Run unlimited bulk jobs (card runs are sequential and capped).

Known limitations

Limitation	Current behavior	Why this boundary exists	If you need this today
Object coverage	DupliCat supports Deal, Contact, Company, Ticket, Order, Project, Quote, activity-record, and Custom Object cloning. Rollout path can vary by object type and the HubSpot surface you use.	Scope set covers supported object families with per-type schema validation and rollout caveats.	Contact support with your object mix, surface, and portal ID before broad rollout.
Template scope	Templates are object-type specific and cannot be applied across different object types.	Prevents invalid config combinations between object models.	Create one template per object type and set portal/personal defaults where needed.
Related activities	Source activities (notes, emails, calls, tasks, meetings) can be copied to the cloned record when selected. Activity types are configurable per clone. DupliCat also adds a source-reference note to the cloned record for traceability.	Activity copying is opt-in to avoid unexpected record multiplication.	Enable related activity copying in your template or clone settings and select the activity types to include.
Attachments	File attachments on source records are not cloned.	Avoids duplicating large files in HubSpot storage.	Re-attach required files to the cloned record manually after clone.
Association copy model	Associations are re-linked to existing associated records; they are not deep-copied by default.	Preserves relationship context while avoiding accidental record multiplication.	Use deep clone only where explicitly supported.
Deal line item behavior	Deal `line_items` can be deep-cloned when selected. Other association types are re-link only.	Deep clone is implemented for the highest-impact deal scenario first.	Validate expected line item output in a test portal before broad rollout.
Field copy boundaries	Protected or conflict-prone fields can be skipped so cloning can complete safely.	Helps avoid failures caused by non-editable or duplicate-restricted fields.	Use writable-only mode and review post-clone records for critical fields.
Empty value handling	Empty properties are not copied by default.	Reduces accidental data overwrite from null/blank source values.	Enable empty-value copying in settings when your workflow requires it.
Bulk processing	Card cloning supports `Number of duplicates (1-10)` sequential duplicates per run with per-duplicate links, but there is no async/batch job runner in this release.	Keeps execution and troubleshooting deterministic for operators.	Run controlled batches in small increments and monitor outcomes after each run.
Change verification	DupliCat does not provide a separate in-app field-history console.	HubSpot already provides field-level change tracking on records.	Open the cloned record in HubSpot and use Property history (with source visible) to verify copied field outcomes.

Security and scope context

Required OAuth scopes and rationale: Scopes and Permissions.
Security controls and handling model: Security and Privacy.

Escalation path

If a limitation blocks your rollout, contact support with:

HubSpot portal ID
Source object type and sample record URL
Expected behavior vs actual behavior
Timestamps/timezone