Merging Wells
Fold duplicate wells into one survivor on the Wells list: preview conflicts, choose what to keep, and remove the source wells from the active list.
When the same well appears more than once in your organization, Merge wells folds the duplicates into a single survivor. After a successful merge, the source wells leave the active Wells list.
Who can merge
Merge is available to users who can manage wells in that scope (typically Division Admin, Region Admin for wells in their regions, or roles with Well Management edit access). Key User and Basic User cannot merge. All wells in the merge must belong to the same organization.
Start a merge
- Go to Wells
- Select two or more specific wells (do not use “select all matching” for merge)
- Open the bulk action Merge wells…
- Work through Configure → Confirm → Execute
The dialog loads a live preview so you can see conflicts and blockers before you commit.
Configure
- Choose the survivor (the well that remains). Every other selected well is a source.
- Resolve differing identity fields (name, API number, and related header values) by picking which value to keep.
- Decide whether to move source simulations onto the survivor. If you leave them behind, they stay with the source wells that are no longer on the active list.
- Optionally open advanced options to replace casing, rods, tubings, or the pumping unit on the survivor, or to acknowledge comparison-set limits when the merge would overflow a set.
Confirm and execute
Review the summary: which well is kept, which wells merge in, simulation and production counts, and any warnings. Then run the merge.
On success you return to the Wells list with one survivor. The source wells are no longer shown in the active list.
What moves onto the survivor
Typical fold behavior:
- Identity fields you selected
- Well details and performance (fill empty values on the survivor)
- Equipment: casing, rods, tubings, pumping unit (survivor wins unless you chose replace)
- Directional surveys
- Production and fluid-shot rows (duplicates skipped)
- Simulations (when you chose to move them), comparisons, and related report links
- Tags, favorites, group and region membership
Exact field handling follows the preview. If something is blocked, the dialog explains why.
Blockers
Merge stays disabled while any of these are true for a source or the set:
- A source well is not available to merge (for example it is already inactive in the system)
- A static or dynamic simulation is pending or running
- A EventHub sync is in progress on a well in the set
Finish or cancel those jobs, then preview again.
Important limits
- Merge is one-way. There is no automatic unmerge.
- Sources leave the active list after the fold. That does not reverse data already applied to the survivor.
- Installed-design conflicts may clear extra installed simulations on the survivor so only one installed design remains.
Related
- Importing wells (imports can land as a new simulation on an existing well when names match)
- Wells overview
- Well data