Clone is a daily micro-action for most users; the value is in knowing exactly what gets copied so the user can adjust the right fields. For admins, knowing when to use record Clone, Clone with Related, or a custom bulk-clone Flow saves hours over months.
- Confirm Clone is available on the relevant object
Standard objects support Clone by default. Custom objects need the Clone action on the page layout or Lightning record page. Check before assuming the button is there.
- Use Clone with Related for parent-child workflows
Renewal opportunities, related cases, quote revisions: Clone with Related is the right tool. Enable per object; users pick which related lists to include on each clone.
- Adjust lookups after cloning if the relationship changed
Lookups copy by default. A cloned record references the same Account or Contact unless the user changes it. Treat lookup review as part of the post-clone discipline.
- Use Permission Set Clone to derive variants
For role variants (Sales Rep, Sales Manager, Senior Sales Rep), clone the base Permission Set and add or remove specific permissions. Cloning prevents drift between related role configurations.
- Use Flow Save As New Version for safe Flow editing
Editing the active version risks production behavior. Save As New Version creates a draft, edit and test the draft, activate when ready.
- Build a bulk-clone Flow for repeated patterns
Renewal cycles, quarterly opportunity rollovers. A Flow with a custom-button trigger plus the right field adjustments is a one-time build that saves hours every quarter.
- Document non-obvious clone behavior in admin training
Auto Number not copying, lookups copying, Edit permission affecting visible fields. Reps who do not know these defaults occasionally create data quality issues.
Standard copies the parent only; Clone with Related copies the parent plus selected related records.
Standard objects support Clone by default; custom objects need explicit page layout or Lightning record page configuration.
Setup-side action that derives a new Permission Set from an existing one as a starting point.
Flow-specific clone that creates a draft version for safe editing.
Flow, Apex, or Data Loader pattern for cloning many records at once.
- Lookup fields copy by default. A cloned Case keeps the same Account and Contact; if the clone is for a different customer, the user must change the lookups.
- Auto Number fields do not copy. The clone receives the next sequence number, which is usually desired but occasionally surprising.
- Edit permission on fields determines what the user sees in the clone form. Partial-edit profiles find some fields unexpectedly blank.
- Flow Save As New Version always creates a new version of the same Flow; it does not create a separate Flow. Use Clone on the Flow definition for a separate Flow.
- Bulk cloning at scale needs governor limit awareness. Flow handles small batches; Apex Batch handles thousands.