This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-05-23. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Article version: Enterprise Server 2.17

Reviewing migration conflicts

After generating a list of migration conflicts, you should review them to ensure that you agree with the default actions ghe-migrator will take when resolving them.

  1. Using a text editor or CSV-compatible spreadsheet software, open conflicts.csv.
  2. With guidance from the examples and reference tables below, review the conflicts.csv file to ensure that the proper actions will be taken upon import.

The conflicts.csv file contains a migration map of conflicts and recommended actions. A migration map lists out both what data is being migrated from the source, and how the data will be applied to the target.


Each row in conflicts.csv provides the following information:

model_nameThe type of data being changed.
source_urlThe source URL of the data.
target_urlThe expected target URL of the data.
recommended_actionThe preferred action ghe-migrator will take when importing the data.

Possible mappings for each record type

There are several different mapping actions that ghe-migrator can take when transferring data:

actionDescriptionApplicable models
import(default) Data from the source is imported to the target.All record types
mapData from the source is replaced by existing data on the target.Users, organizations, repositories
renameData from the source is renamed, then copied over to the target.Users, organizations, repositories
map_or_renameIf the target exists, map to that target. Otherwise, rename the imported model.Users
mergeData from the source is combined with existing data on the target.Teams

We strongly suggest you review the conflicts.csv file and use ghe-migrator audit to ensure that the proper actions are being taken. If everything looks good, you can continue to "Applying the imported data on GitHub Enterprise Server".

Ask a human

Can't find what you're looking for?

Contact us