Completing your live migration from GitHub Enterprise Server to GHE.com

After you have run a migration with the ELM CLI tool, there are some follow-up tasks to complete.

Restore users' access

Because GitHub Enterprise Server and GHE.com use different provisioning and authentication systems, organization membership is not carried over between platforms. You will need to add users to the organization before you can reattribute activity to them in a migrated repository.

If you created a new organization for the migration process, add members to the organization. You can do this manually, but many enterprises manage organization membership from their identity provider (IdP) by syncing enterprise teams with IdP groups.
Add organization members to the migrated repositories.

Reattribute activity to users

After you run a migration with GitHub Enterprise Importer or Enterprise Live Migrations, all user activity in the migrated repository (except Git commits) is attributed to placeholder identities called mannequins. For more information, see Mannequins and user activity.

Once user accounts have been added to the organization on GHE.com, you can invite users to reclaim a mannequin's activity. You can do this in the browser or, with the ELM CLI tool, reclaim mannequins in bulk without the invite process.

Reclaiming mannequins in bulk using the ELM CLI

You can use the ELM CLI to reclaim mannequins in bulk.

Generate the list of mannequins in the migration. The following command produces a CSV file that maps mannequins to organization members. Optionally, to include mannequins that have already been reclaimed, add the --include-reclaimed flag.
Shell
```
gh target mannequin list ORGANIZATION_NAME
```
```
gh target mannequin list ORGANIZATION_NAME
```
This will produce a CSV file of all mannequins in the target organization, in the form mannequin-user,mannequin-id,target-user:
```
ghe-admin,M_kgDOAAw-zw,
unit-test,M_kgDOAA5FYg,
admin-octoshift,M_kgDOAA5FZw,
```

Output the command to a file that you can edit.

Shell

gh elm target mannequin list ORGANIZATION_NAME > MANNEQUINS.csv

gh elm target mannequin list ORGANIZATION_NAME > MANNEQUINS.csv

Edit the CSV file, adding the username of the organization member that corresponds to each mannequin. Ensure you save the file after you edit it.

Reclaim mannequins using the mannequin reclaim command. Use the ORGANIZATION_NAME and filename from the previous step.

Shell

gh target mannequin reclaim ORGANIZATION_NAME --csv MANNEQUINS.csv

gh target mannequin reclaim ORGANIZATION_NAME --csv MANNEQUINS.csv

For a full reference of the reclaim command, including options to control invitations and prompting, see Enterprise Live Migrations CLI reference.

Reclaiming mannequins in the browser

In the upper-right corner of GitHub, click your profile picture, then click Organizations.
Select an organization by clicking on it.
Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.
In the "Access" section of the sidebar, click Import/Export.
To the right of the mannequin you want to reclaim, click Reattribute.
In the search field, type the username of the organization member you want to attribute the mannequin's contributions to, then click the member.

Note

You can only send attribution invitations to user accounts that are already members of the organization.
Click Invite. By default, the organization member will receive an invitation via email, and the mannequin will not be reclaimed until the member accepts the invitation.

Reattribute Git activity

Authorship for Git commits is not associated with mannequins and cannot be attributed to GitHub users by reclaiming mannequins. Instead, commit authorship is attributed to user accounts on GitHub based on the email address that was used to author the commit in Git.

To reattribute Git activity on GHE.com, ensure the user's primary email address in your identity provider (IdP) matches the email address used for their commits. With Enterprise Managed Users, users cannot add email addresses to their user account on GitHub, so users will not be able to reattribute their Git commits independently.

Recreate organization settings

If you created a new organization for the migration process, restore settings such as policies, organization teams, and projects.