Import and export settings | GitLab Docs
/ Import and export settings Tier : Free, Premium, Ultimate Offering : GitLab Self-Managed, GitLab Dedicated Settings for import- and export-related features. Configure allowed import sources Before you can import projects from other systems, you must enable the import source for that system. Sign in to GitLab as a user with Administrator access level. In the upper-right corner, select Admin . In the left sidebar, select Settings > General .
Expand the Import and export settings section. Select each of Import sources to allow. Select Save changes . Disable unused import sources Only import projects from sources you trust. If you import a project from an untrusted source, an attacker could steal your sensitive data. For example, an imported project with a malicious .gitlab-ci.yml file could allow an attacker to exfiltrate group CI/CD variables. GitLab Self-Managed administrators can reduce their attack surface by disabling import sources they don’t need: In the upper-right corner, select Admin .
In the left sidebar, select Settings > General . Expand Import and export settings . Scroll to Import sources . Clear checkboxes for importers that are not required. Enable project export To enable the export of projects and their data : Sign in to GitLab as a user with Administrator access level. In the upper-right corner, select Admin . In the left sidebar, select Settings > General . Expand the Import and export settings section.
Scroll to Project export . Select the Enabled checkbox. Select Save changes . Enable migration of groups and projects by direct transfer Generally available in GitLab 18.3. Migration of groups and projects by direct transfer is disabled by default. To enable migration of groups and projects by direct transfer: Sign in to GitLab as a user with Administrator access level. In the upper-right corner, select Admin . In the left sidebar, select Settings > General .
Expand the Import and export settings section. Scroll to Allow migrating GitLab groups and projects by direct transfer . Select the Enabled checkbox. Select Save changes . The same setting is available in the API as the bulk_import_enabled attribute. Enable export of groups and projects for offline transfer Introduced in GitLab 19.3 with a feature flag named offline_transfer_exports . Disabled by default. The availability of this feature is controlled by a feature flag.
For more information, see the history. Prerequisites: You must be an administrator. Turn on this setting to allow users to create offline transfer exports of groups and projects. To enable export of groups and projects for offline transfer: In the upper-right corner, select Admin . In the left sidebar, select Settings > General . Expand the Import and export settings section. Scroll to Allow exporting GitLab groups and projects by offline transfer .
Select the Enabled checkbox. Select Save changes . The same setting is available in the API as the offline_transfer_exports_enabled attribute. Enable import of groups and projects by offline transfer Introduced in GitLab 19.3 with a feature flag named offline_transfer_imports . Disabled by default. The availability of this feature is controlled by a feature flag. For more information, see the history. Prerequisites: You must be an administrator.
Turn on this setting to allow users to import groups and projects from an offline transfer export. To enable import of groups and projects by offline transfer: In the upper-right corner, select Admin . In the left sidebar, select Settings > General . Expand the Import and export settings section. Scroll to Allow importing GitLab groups and projects by offline transfer . Select the Enabled checkbox. Select Save changes .
The same setting is available in the API as the offline_transfer_imports_enabled attribute. Allow S3-compatible object storage for offline transfer Introduced in GitLab 18.9 with a feature flag named offline_transfer_exports . Disabled by default. The availability of this feature is controlled by a feature flag. For more information, see the history. Prerequisites: You must be an administrator. By default, offline transfer supports only AWS S3 and Google Cloud Storage.
Turn on this setting to also allow S3-compatible providers, such as MinIO. When you enable this setting, users who can perform offline transfers can supply an arbitrary endpoint URL in the offline transfer object storage configuration. GitLab then sends requests to that endpoint. Enable this setting only if you trust the users who can perform offline transfers. To allow S3-compatible object storage for offline transfer: In the upper-right corner, select Admin .
In the left sidebar, select Settings > General . Expand the Import and export settings section. Scroll to Allow S3 compatible object storage for offline transfer . Select the Enabled checkbox. Select Save changes . Allow application default credentials for offline transfer Introduced as an experiment in GitLab 19.3 with feature flags named offline_transfer_exports , offline_transfer_imports , and offline_transfer_ui .
Disabled by default. The availability of this feature is controlled by a feature flag. For more information, see the history. Turn on this setting to allow offline transfer to authenticate with Google Cloud Storage by using Application Default Credentials (ADC). With every other object storage provider, the user who creates an export or an import supplies the credentials. With ADC, no user supplies credentials. GitLab stores only the Google Cloud project ID and resolves the credentials for each request from the environment of the instance, either from the Compute Engine metadata server or from the GOOGLE_APPLICATION_CREDENTIALS environment variable.
Prerequisites: You must be an administrator. An offline transfer that uses ADC acts with every Cloud Storage permission that the service account of the instance holds. That service account is usually more privileged than any individual user, so a user who creates an ADC transfer can reach buckets they hold no credentials for. To limit this risk, GitLab applies the following restrictions, which you cannot turn off: Only users with administrator access can create an offline transfer export or import that uses ADC.
Other users receive the error Only administrators can use Application Default Credentials for offline transfer. The bucket name must start with gitlab-offline-transfer- . This prefix keeps ADC transfers away from the buckets that the instance uses for its own object storage, such as uploads, job artifacts, and LFS objects. ADC is not available on GitLab.com. The Google Cloud project ID that you provide for a transfer does not limit which buckets that transfer can reach.
Bucket names are globally unique in Cloud Storage, so an ADC transfer can use any bucket that the service account can access and whose name starts with gitlab-offline-transfer- , in any Google Cloud project. GitLab checks these restrictions when a user creates a transfer. If you turn off this setting, users can no longer create ADC transfers, but transfers that already started continue to run. To allow Application Default Credentials for offline transfer: In the upper-right corner, select Admin .
In the left sidebar, select Settings > General . Expand the Import and export settings section. Scroll to Allow Google Cloud Application Default Credentials for offline transfer . Select the Enabled checkbox. Select Save changes . The same setting is available in the API as the allow_application_default_credentials_for_offline_transfer attribute. Enable silent admin exports Introduced in GitLab 17.0 with a feature flag named export_audit_events .
Disabled by default. Generally available in GitLab 17.1. Feature flag export_audit_events removed. Introduced for file export downloads in GitLab 17.1. Enable silent admin exports to prevent audit events when instance administrators trigger a project or group file export or download the export file. Exports from non-
The rest of this page is on the live site.