Import and export conflict resolution

If duplicate content is found during import, you must select one of these options in the dialog box:

Skip & Import:
- Existing items with the same name are not imported (they are skipped).
- Items that exist locally but are not in the import file remain unchanged.
- New items from the import file are added.
- No changes are made to the existing content that conflicts with the import.
Merge:
- Existing items with the same name are merged:
  - Content from the import file is combined with the existing content.
  - For some items, specific fields or sub-items may be overwritten or added.
- Items that exist locally but are not in the import file remain unchanged.
- New items from the import file are added.
- Use this option to preserve and combine both existing and imported data.
Overwrite:
- Existing items with the same name are completely replaced; content in the destination is removed and replaced with content from the import file.
- Items that exist locally but are not in the import file remain unchanged.
- New items from the import file are added.
- Use this option to discard the existing content for conflicting items and use only the imported version.

The table below shows the detailed differences for each import option:

Duplicate anchors import

When you import items, the program checks for duplicate anchors between the import file and the destination tenant. If the program detects a conflict, a modal is displayed. The modal shows a description of the conflict, a link to download a conflict report, and options to cancel or continue import. The program reassigns anchor order for affected items after the import. The program applies this check only to new objects in the import file.

Relation Mapping Import

When you import items, the program checks whether any relation mappings in the import file refer to objects that don't exist in the destination tenant. If the program detects a conflict, a modal is displayed. The modal shows a description of the conflict, a link to download a conflict report, and options to cancel or continue import. The program doesn't import relation mappings that refer to missing objects. The program applies this check at the object level and at the process level.

Content Type	On Skip & Import	On Merge	On Overwrite
CloudSuites	CloudSuites with the same name as existing ones are not imported. CloudSuites that exist locally but not in the import file remain unchanged. New CloudSuites from the import file are added.	CloudSuites with the same name as existing ones are merged (content in destination is combined with content from the import file). CloudSuites that exist locally but not in the import file remain unchanged. New CloudSuites from the import file are added.	CloudSuites with the same name as existing ones are overwritten (content in destination is replaced with content from the import file). CloudSuites that exist locally but not in the import file remain unchanged. New CloudSuites from the import file are added.
Processes	Processes with the same name as existing ones are not imported. Processes that exist locally but not in the import file remain unchanged. New Processes from the import file are added.	Processes with the same name as existing ones are merged (content in destination is combined with content from the import file). Processes that exist locally but not in the import file remain unchanged. New Processes from the import file are added.	Processes with the same name as existing ones are overwritten (content in destination is replaced with content from the import file). Processes that exist locally but not in the import file remain unchanged. New Processes from the import file are added.
Objects	Objects with the same name as existing ones are not imported. Objects that exist locally but not in the import file remain unchanged. New Objects from the import file are added.	Objects with the same name as existing ones are merged (content in destination is combined with content from the import file). Objects that exist locally but not in the import file remain unchanged. New Objects from the import file are added. Note: Objects that belong to different processes in the import file and destination file are merged in the destination process.	Objects with the same name as existing ones are overwritten (content in destination is replaced with content from the import file). Objects that exist locally but not in the import file remain unchanged. New Objects from the import file are added. Note: Objects that belong to different processes in the import file and destination file are overwritten in the destination process.
Events	All events are not imported when the object is skipped.	Events with the same name as existing ones are merged. That means category and registry entry in destination file are replaced with those from the import file. Events that exist locally but not in the import file remain unchanged. New events from the import file are added.	All events in destination are removed. All events from the import file are added.
Attributes	All attributes are not imported when the object is skipped.	Attributes with the same name as existing ones are merged. That means the type in destination file is replaced with type from the import file. Attributes that exist locally but not in the import file remain unchanged. New attributes from the import file are added.	All attributes in destination are removed. All attributes from the import file are added.
Scripts	All scripts are not imported when the object is skipped.	Scripts with the same name as existing ones are merged. That means the type in destination is replaced with type from the import file. Scripts that exist locally but not in the import file remain unchanged. New scripts from the import file are added.	All scripts in destination are removed. All scripts from the import file are added.
Insights	Insights with the same name as existing ones are not imported. Insights that exist locally but not in the import file remain unchanged. New Insights from the import file are added.	Insights with the same name as existing ones are merged. That means the content in destination is combined with content from the import file. Insights that exist locally but not in the import file remain unchanged. New Insights from the import file are added.	Insights with the same name as existing ones are overwritten. That means the content in destination is replaced with content from the import file. Insights that exist locally but not in the import file remain unchanged. New Insights from the import file are added.
Objects used in Insight	Selection is not imported when the Insight is skipped.	Selected objects that exist in both import and destination remain selected. Selected objects that exist locally but not in the import file remain selected. New selected objects from the import file are added and selected.	Selected objects that exist locally but not in the import file are unselected. All selected objects from the import file are added and selected.
Insight Prompts (genAI)	Insight prompts are not imported when the Insight is skipped.	Insight prompts that exist locally but not in the import file are removed. Insight prompts from the import file are added.	Insight prompts in destination are removed. Insight prompts from the import file are added.
Object Colors	Insight colors are not imported when the Insight is skipped.	Insight colors that exist locally but not in the import file are removed. Insight colors from the import file are added.	Insight colors in destination are removed. Insight colors from the import file are added.
Pages	All pages are not imported when the Insight is skipped .	Pages with the same name as existing ones are left unchanged. Duplicate pages are added as new pages with a unique name. Pages that exist locally but not in the import file remain unchanged. New pages from the import file are added.	All pages in destination are removed. All pages from the import file are added.
Page Prompts (genAI)	All page prompts are not imported when the Insight is skipped.	Page prompts that already exist are left unchanged. Duplicate pages are added as new pages with their prompts. Page prompts that exist locally but not in the import file remain unchanged. New page prompts from the import file are added.	Page prompts in destination are removed. Page prompts from the import file are added.
Widgets	All widgets are not imported when the page is not imported. Widgets published to Workspace in the import file are not imported.	Widgets in pages that already exist are left unchanged. Widgets in duplicate pages are added in the new pages. Widgets in pages that exist locally but not in the import file remain unchanged. Widgets in new pages from the import file are added. Published widgets to Workspace in the import file are also published in the destination.	Widgets in pages that exist locally but not in the import file are removed. Widgets in pages from the import file are added. Published widgets to Workspace in the import file are also published in the destination.
Conformance widget - BPMNs	Conformance widget is not imported when the page is skipped; the existing conformance widget in a page is not updated.	This follows the Process Modeler content duplicate behavior. If you select MERGE: BPMN models with the same name as the existing ones receive a new version added with status Approved. Models that exist locally but not in the import file remain unchanged. New models from the import file are added with version 1 and status Approved. If you select SMART MERGE: BPMN models with the same name as the existing ones receive a new version added with status Approved. Models that exist locally but not in the import file are removed. New models from the import file are added with version 1 and status Approved. If you select OVERWRITE: BPMN models with the same name as the existing ones are replaced with the model from the import file (version set to 1, status Approved) Models that exist locally but not in the import file are removed. New models from the import file are added with version 1 and status Approved.	(Same as Merge)
Conformance mapping	Conformance widget is not imported when the page is skipped. The existing mappings are not updated.	Mappings of BPMNs with the same name as existing ones are overwritten with mappings from the import file. Mappings of BPMNs that exist locally but not in the import file remain unchanged. New mappings of BPMNs from the import file are added.	Mappings of BPMNs with the same name as existing ones are overwritten. That means the conformance widget is fully replaced. Mappings of BPMNs that exist locally but not in the import file are removed. New mappings of BPMNs from the import file are added. That means a new conformance widget is added.
Conformance Violations	All violations are not imported.	Conflicting violations (same name and type) are overwritten. Violations that exist locally but not in the import file remain unchanged. New violations from the import file are added.	All violations in destination are removed. All violations from the import file are added.
Event Level Metrics	All metrics are not imported.	Conflicting metrics (same name and type) are overwritten. Metrics that exist locally but not in the import file remain unchanged. New metrics from the import file are added.	All metrics in destination are removed. All metrics from the import file are added.