Skip to main content

Org Merge

Prepare this org for a merge by identifying what to keep, replace, or retire and highlighting dependencies.

Tess Geri avatar
Written by Tess Geri
Updated over 4 months ago

Logic Inventory by Object (Opportunity)

I’m preparing to merge orgs. List all automation and logic on the
Opportunity object: Flows, Apex Triggers, Validation Rules, and
Approval Processes. Include a short description of what each one
does, if available.

Flows with Similar Field Updates

Identify active Flows that update the same field(s) on the same 
object β€” for example, multiple Flows that set Lead.Status or
Opportunity.Stage. List the Flow names, target object, and
field(s) involved. Flag them for potential consolidation.

Redundant Task Creation Logic

Are there multiple Flows or Apex Triggers that create follow-up 
Tasks? List each component, the trigger conditions, and Task details
(e.g. subject, due date logic) so we can assess redundancy during
the merge.

Assignment Logic Overlap

List Flows or Apex Triggers that include assignment logic β€” such 
as setting OwnerId or assigning queue/user. For each, include the
object, entry conditions, and assignment type. Highlight if multiple
components target the same field.

Object-Level Merge Risk Assessment (Lead)

For the Lead object, review metadata and flag components that might 
create conflicts in a merge β€” such as hardcoded values, overlapping
validation rules, or highly customized automation.
Did this answer your question?