Importing will not be possible if the import instance version differs from that of the exporter.

For existing installations, the project import option has to be enabled in application settings (/admin/application_settings) under 'Import sources'. Ask your administrator if you don't see the GitLab export button when creating a new project.

You can find some useful raketasks if you are an administrator in the import_export raketask.

The exports are stored in a temporary shared directory and are deleted every 24 hours by a specific worker.

Group members will get exported as project members, as long as the user has master or admin access to the group where the exported project lives. An admin in the import side is required to map the users, based on email or username. Otherwise, a supplementary comment is left to mention the original author and the MRs, notes or issues will be owned by the importer.

Existing projects running on any GitLab instance or GitLab.com can be exported with all their related data and be moved into a new GitLab instance.

The table reflects what GitLab version we updated the Import/Export version at. For instance, 8.10.3 and 8.11 will have the same Import/Export version (0.1.3) and the exports between them will be compatible.

The new GitLab project import feature is at the far right of the import options when creating a New Project. Make sure you are in the right namespace and you have entered a project name. Click on GitLab export:

You can see where the project will be imported to. You can now select file exported previously: