diff --git a/app/views/groups/_import_group_from_file_panel.html.haml b/app/views/groups/_import_group_from_file_panel.html.haml
index c39f5cf87c73da4f3c66738bf93e2747919b7aef..43a8ccdaae48dbe478470235bd37e7b8b8fa8756 100644
--- a/app/views/groups/_import_group_from_file_panel.html.haml
+++ b/app/views/groups/_import_group_from_file_panel.html.haml
@@ -10,14 +10,14 @@
       alert_options: { class: 'gl-mb-5' },
       dismissible: false) do |c|
       - c.with_body do
-        - docs_link_start = '<a href="%{url}" target="_blank" rel="noopener noreferrer">'.html_safe % { url: help_page_path('user/group/import/index', anchor: 'migrate-groups-by-direct-transfer-recommended') }
+        - docs_link_start = '<a href="%{url}" target="_blank" rel="noopener noreferrer">'.html_safe % { url: help_page_path('user/group/import/index') }
         - link_end = '</a>'.html_safe
         = s_('GroupsNew|This feature is deprecated and replaced by group migration by direct transfer. %{docs_link_start}Learn more%{docs_link_end}.').html_safe % { docs_link_start: docs_link_start, docs_link_end: link_end }
     = render 'shared/groups/group_name_and_path_fields', f: f
     .form-group
       = f.label :file, s_('GroupsNew|Upload file')
       .gl-font-weight-normal
-        - import_export_link_start = '<a href="%{url}" target="_blank">'.html_safe % { url: help_page_path('user/group/import/index') }
+        - import_export_link_start = '<a href="%{url}" target="_blank">'.html_safe % { url: help_page_path('user/project/settings/import_export', anchor: 'migrate-groups-by-uploading-an-export-file-deprecated') }
         = s_('GroupsNew|To import a group, navigate to the group settings for the GitLab source instance, %{link_start}generate an export file%{link_end}, and upload it here.').html_safe % { link_start: import_export_link_start, link_end: '</a>'.html_safe }
       .gl-mt-3
         = render 'shared/file_picker_button', f: f, field: :file, help_text: nil
diff --git a/app/views/groups/settings/_export.html.haml b/app/views/groups/settings/_export.html.haml
index ff1d76f470c70d556a2398de8e761faa3e7d73a4..c7909a7c2490a2418d185ce57108e6c9af2c71a5 100644
--- a/app/views/groups/settings/_export.html.haml
+++ b/app/views/groups/settings/_export.html.haml
@@ -10,7 +10,7 @@
   - c.with_body do
     = render Pajamas::AlertComponent.new(variant: :warning, dismissible: false, alert_options: { class: 'gl-mb-4' }) do |c|
       - c.with_body do
-        - docs_link_start = '<a href="%{url}" target="_blank" rel="noopener noreferrer">'.html_safe % { url: help_page_path('user/group/import/index', anchor: 'migrate-groups-by-direct-transfer-recommended') }
+        - docs_link_start = '<a href="%{url}" target="_blank" rel="noopener noreferrer">'.html_safe % { url: help_page_path('user/group/import/index') }
         - docs_link_end = '</a>'.html_safe
         = s_('GroupsNew|This feature is deprecated and replaced by group migration by direct transfer. %{docs_link_start}Learn more%{docs_link_end}.').html_safe % { docs_link_start: docs_link_start, docs_link_end: docs_link_end }
     %p
diff --git a/doc/administration/backup_restore/restore_gitlab.md b/doc/administration/backup_restore/restore_gitlab.md
index 2dd85602f993b4af1e169efded7c86fc3f3a7272..51ada659acd4a255ef393212d043b5bb73e65835 100644
--- a/doc/administration/backup_restore/restore_gitlab.md
+++ b/doc/administration/backup_restore/restore_gitlab.md
@@ -282,7 +282,8 @@ project or group from there:
    the backed-up instance from which you want to restore.
 1. [Restore the backup](#restore-gitlab) into this new instance, then
    export your [project](../../user/project/settings/import_export.md)
-   or [group](../../user/group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated). For more information about what is and isn't exported, see the export feature's documentation.
+   or [group](../../user/project/settings/import_export.md#migrate-groups-by-uploading-an-export-file-deprecated). For
+   more information about what is and isn't exported, see the export feature's documentation.
 1. After the export is complete, go to the old instance and then import it.
 1. After importing the projects or groups that you wanted is complete, you may
    delete the new, temporary GitLab instance.
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md
index 336ed743a47d5572ec154fc90bfbd74bc7f798c6..f5a50c6e9a34460f0be904a735806579acec71d3 100644
--- a/doc/administration/get_started.md
+++ b/doc/administration/get_started.md
@@ -150,7 +150,7 @@ Backups of GitLab databases and file systems are taken every 24 hours, and are k
 - You can use the project export option in:
   - [The UI](../user/project/settings/import_export.md#export-a-project-and-its-data).
   - [The API](../api/project_import_export.md#schedule-an-export).
-- [Group export by uploading a file export](../user/group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated)
+- [Group export by uploading a file export](../user/project/settings/import_export.md#migrate-groups-by-uploading-an-export-file-deprecated)
   does **not** export the projects in it, but does export:
   - Epics
   - Milestones
diff --git a/doc/administration/settings/import_and_export_settings.md b/doc/administration/settings/import_and_export_settings.md
index ddb31e494838513b30d9d8926a17eabcd488ee75..54995cdc68650ab629da859a2b4d6cb924d515ed 100644
--- a/doc/administration/settings/import_and_export_settings.md
+++ b/doc/administration/settings/import_and_export_settings.md
@@ -121,7 +121,7 @@ To modify this setting:
 > - **Maximum decompressed file size for archives from imports** field [renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/130081) from **Maximum decompressed size** in GitLab 16.4.
 
 When you import a project using [file exports](../../user/project/settings/import_export.md) or
-[direct transfer](../../user/group/import/index.md#migrate-groups-by-direct-transfer-recommended), you can specify the
+[direct transfer](../../user/group/import/index.md), you can specify the
 maximum decompressed file size for imported archives. The default value is 25 GiB.
 
 When you import a compressed file, the decompressed size cannot exceed the maximum decompressed file size limit. If the
diff --git a/doc/api/bulk_imports.md b/doc/api/bulk_imports.md
index 1d7556f863a66672ef0001b8c3ce148b56b3c07e..bebfdb80a35174bf5cb10117afc459bd7067ee89 100644
--- a/doc/api/bulk_imports.md
+++ b/doc/api/bulk_imports.md
@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - Project migration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/390515) in GitLab 15.11.
 
 With the group migration by direct transfer API, you can start and view the progress of migrations initiated with
-[group migration by direct transfer](../user/group/import/index.md#migrate-groups-by-direct-transfer-recommended).
+[group migration by direct transfer](../user/group/import/index.md).
 
 WARNING:
 Migrating projects with this API is in [Beta](../policy/experiment-beta-support.md#beta). This feature is not
diff --git a/doc/api/group_import_export.md b/doc/api/group_import_export.md
index 7a3b031f18aadd4ec518d601832b30f861233120..7e065dd87d20cdd17659683485392942458f180e 100644
--- a/doc/api/group_import_export.md
+++ b/doc/api/group_import_export.md
@@ -32,7 +32,7 @@ To preserve the member list and their respective permissions on imported groups,
 ## Prerequisites
 
 - For information on prerequisites for group import and export API, see prerequisites for
-  [migrating groups by uploading an export file](../user/group/import/index.md#preparation).
+  [migrating groups by uploading an export file](../user/project/settings/import_export.md#preparation).
 
 ## Schedule new export
 
diff --git a/doc/api/group_relations_export.md b/doc/api/group_relations_export.md
index e1c0cd81bd6144dfd5aebe9d86318d504f89949d..bd48fb13ec6f5965d7897ac6bb35fe18a5b19dd6 100644
--- a/doc/api/group_relations_export.md
+++ b/doc/api/group_relations_export.md
@@ -13,7 +13,7 @@ top-level
 relation (for example, milestones, boards, and labels).
 
 The group relations export API is primarily used in
-[group migration by direct transfer](../user/group/import/index.md#migrate-groups-by-direct-transfer-recommended)
+[group migration by direct transfer](../user/group/import/index.md)
 and
 can't be used with the [group import and export API](group_import_export.md).
 
diff --git a/doc/api/project_relations_export.md b/doc/api/project_relations_export.md
index 5fe3923edc8e2683aa25a5c7f72fbd1980564189..a586c940b8ef4026ca558bff8d8ab32185720806 100644
--- a/doc/api/project_relations_export.md
+++ b/doc/api/project_relations_export.md
@@ -16,7 +16,7 @@ top-level
 relation (for example, milestones, issues, and labels).
 
 The project relations export API is primarily used in
-[group migration](../user/group/import/index.md#migrate-groups-by-direct-transfer-recommended) can't
+[group migration](../user/group/import/index.md) can't
 be used with the
 [project import and export API](project_import_export.md).
 
diff --git a/doc/development/bulk_import.md b/doc/development/bulk_import.md
index 6c0bed8e204b375324e4eb7f062838e6bdc04fe5..752bcbbac19ea8f3bda6c00a6029bd4b21f648a2 100644
--- a/doc/development/bulk_import.md
+++ b/doc/development/bulk_import.md
@@ -12,7 +12,7 @@ NOTE:
 To use direct transfer, ensure your GitLab installation is accessible from
 [GitLab IP addresses](../user/gitlab_com/index.md#ip-range) and has a public DNS entry.
 
-[Group migration by direct transfer](../user/group/import/index.md#migrate-groups-by-direct-transfer-recommended) is the
+[Group migration by direct transfer](../user/group/import/index.md) is the
 evolution of migrating groups and projects using file exports. The goal is to have an easier way for the user to migrate a whole group,
 including projects, from one GitLab instance to another.
 
@@ -36,8 +36,8 @@ idea is to have one ETL pipeline for each relation to be imported.
 
 ### API
 
-The current [project](../user/project/settings/import_export.md) and
-[group](../user/group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated) imports are file based, so
+The current [project](../user/project/settings/import_export.md#migrate-projects-by-uploading-an-export-file) and
+[group](../user/project/settings/import_export.md#migrate-groups-by-uploading-an-export-file-deprecated) imports are file based, so
 they require an export step to generate the file to be imported.
 
 Group migration by direct transfer leverages the [GitLab API](../api/rest/index.md) to speed the migration.
diff --git a/doc/user/gitlab_com/index.md b/doc/user/gitlab_com/index.md
index a7b7553480085e26c77930daf9d997d988b5d698..75d0c8fdd1262573f9b00595abfe412458f6c601 100644
--- a/doc/user/gitlab_com/index.md
+++ b/doc/user/gitlab_com/index.md
@@ -245,7 +245,7 @@ which GitLab you use:
 | [Bitbucket Server](../project/import/bitbucket_server.md)                                           | **{check-circle}** Yes | **{dotted-circle}** No      |
 | [FogBugz](../project/import/fogbugz.md)                                                             | **{check-circle}** Yes | **{dotted-circle}** No      |
 | [Gitea](../project/import/gitea.md)                                                                 | **{check-circle}** Yes | **{dotted-circle}** No      |
-| [GitLab by direct transfer](../group/import/index.md#migrate-groups-by-direct-transfer-recommended) | **{check-circle}** Yes | **{dotted-circle}** No      |
+| [GitLab by direct transfer](../group/import/index.md)                                               | **{check-circle}** Yes | **{dotted-circle}** No      |
 | [GitLab using file exports](../project/settings/import_export.md)                                   | **{check-circle}** Yes | **{dotted-circle}** No      |
 | [GitHub](../project/import/github.md)                                                               | **{check-circle}** Yes | **{dotted-circle}** No      |
 | [Manifest file](../project/import/manifest.md)                                                      | **{check-circle}** Yes | **{dotted-circle}** No      |
@@ -454,7 +454,7 @@ To help avoid abuse, the following are rate limited:
 For more information, see:
 
 - [Project import/export rate limits](../../user/project/settings/import_export.md#rate-limits).
-- [Group import/export rate limits](../../user/group/import/index.md#rate-limits).
+- [Group import/export rate limits](../../user/project/settings/import_export.md#rate-limits-1).
 
 ### Non-configurable limits
 
diff --git a/doc/user/group/import/index.md b/doc/user/group/import/index.md
index 288788550980eac49d2520b3593b1035f9909ff3..dfc5332921d659872ee6dd6dc664a30ca569fe53 100644
--- a/doc/user/group/import/index.md
+++ b/doc/user/group/import/index.md
@@ -4,7 +4,14 @@ group: Import and Integrate
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Migrating GitLab groups **(FREE ALL)**
+# Migrate GitLab groups and projects by using direct transfer **(FREE ALL)**
+
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/249160) in GitLab 13.7 for group resources [with a flag](../../feature_flags.md) named `bulk_import`. Disabled by default.
+> - Group items [enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/338985) in GitLab 14.3.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/267945) in GitLab 14.4 for project resources [with a flag](../../feature_flags.md) named `bulk_import_projects`. Disabled by default.
+> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.6.
+> - New application setting `bulk_import_enabled` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383268) in GitLab 15.8. `bulk_import` feature flag removed.
+> - `bulk_import_projects` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.10.
 
 You can migrate GitLab groups:
 
@@ -16,19 +23,10 @@ You can migrate GitLab groups:
 You can migrate groups in two ways:
 
 - By direct transfer (recommended).
-- By uploading an export file.
+- By [uploading an export file](../../project/settings/import_export.md).
 
 If you migrate from GitLab.com to self-managed GitLab, an administrator can create users on the self-managed GitLab instance.
 
-## Migrate groups by direct transfer (recommended)
-
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/249160) in GitLab 13.7 for group resources [with a flag](../../feature_flags.md) named `bulk_import`. Disabled by default.
-> - Group items [enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/338985) in GitLab 14.3.
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/267945) in GitLab 14.4 for project resources [with a flag](../../feature_flags.md) named `bulk_import_projects`. Disabled by default.
-> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.6.
-> - New application setting `bulk_import_enabled` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/383268) in GitLab 15.8. `bulk_import` feature flag removed.
-> - `bulk_import_projects` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.10.
-
 On self-managed GitLab, by default [migrating group items](#migrated-group-items) is not available. To show the
 feature, an administrator can [enable it in application settings](../../../administration/settings/import_and_export_settings.md#enable-migration-of-groups-and-projects-by-direct-transfer).
 
@@ -59,12 +57,12 @@ We invite you to leave your feedback about migrating by direct transfer in
 If you want to move groups instead of copying groups, you can [transfer groups](../manage.md#transfer-a-group) if the
 groups are in the same GitLab instance. Transferring groups is a faster and more complete option.
 
-### Known issues
+## Known issues
 
 See [epic 6629](https://gitlab.com/groups/gitlab-org/-/epics/6629) for a list of known issues for migrating by direct
 transfer.
 
-### Estimating migration duration
+## Estimating migration duration
 
 Estimating the duration of migration by direct transfer is difficult. The following factors affect migration duration:
 
@@ -111,7 +109,7 @@ There's no exact formula to reliably estimate a migration. However, the average
 
 If you are migrating large projects and encounter problems with timeouts or duration of the migration, see [Reducing migration duration](#reducing-migration-duration).
 
-### Limits
+## Limits
 
 > Eight hour time limit on migrations [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/429867) in GitLab 16.7.
 
@@ -138,7 +136,7 @@ You can test the maximum relation size limit using these APIs:
 
 If either API produces files larger than the maximum relation size limit, group migration by direct transfer fails.
 
-### Visibility rules
+## Visibility rules
 
 After migration:
 
@@ -154,7 +152,7 @@ After migration:
 If you used a private network on your source instance to hide content from the general public,
 make sure to have a similar setup on the destination instance, or to import into a private group.
 
-### Prerequisites
+## Prerequisites
 
 > Requirement for Maintainer role instead of Developer role introduced in GitLab 16.0 and backported to GitLab 15.11.1 and GitLab 15.10.5.
 
@@ -181,7 +179,7 @@ To migrate groups by direct transfer:
   - [Configure `proxy_download`](../../../administration/object_storage.md#configure-the-common-parameters).
   - Ensure that the destination GitLab instance has access to the object storage of the source GitLab instance.
 
-### Prepare user accounts
+## Prepare user accounts
 
 To ensure GitLab maps users and their contributions correctly:
 
@@ -196,7 +194,7 @@ To ensure GitLab maps users and their contributions correctly:
 1. If users already exist on the destination instance and you use [SAML SSO for GitLab.com groups](../../group/saml_sso/index.md), all users must
    [link their SAML identity to their GitLab.com account](../../group/saml_sso/index.md#link-saml-to-your-existing-gitlabcom-account).
 
-### Connect the source GitLab instance
+## Connect the source GitLab instance
 
 Create the group you want to import to and connect the source GitLab instance:
 
@@ -209,7 +207,7 @@ Create the group you want to import to and connect the source GitLab instance:
 1. Enter the [personal access token](../../../user/profile/personal_access_tokens.md) for your source GitLab instance.
 1. Select **Connect instance**.
 
-### Select the groups and projects to import
+## Select the groups and projects to import
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/385689) in GitLab 15.8, option to import groups with or without projects.
 
@@ -228,7 +226,7 @@ WARNING:
 Importing groups with projects is in [Beta](../../../policy/experiment-beta-support.md#beta). This feature is not
 ready for production use.
 
-### Group import history
+## Group import history
 
 > **Partially completed** status [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/394727) in GitLab 16.7.
 
@@ -248,7 +246,7 @@ To view group import history:
 1. In the upper-right corner, select **History**.
 1. If there are any errors for a particular import, select **See failures** to see their details.
 
-### Review results of the import
+## Review results of the import
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/429109) in GitLab 16.6 [with a flag](../../feature_flags.md) named `bulk_import_details_page`. Enabled by default.
 
@@ -257,7 +255,7 @@ To review the results of an import:
 1. Go to the [Group import history page](#group-import-history).
 1. To see the details of a failed import, select the **See failures** link on any import with a **Failed** or **Partially completed** status.
 
-### Migrated group items
+## Migrated group items
 
 The group items that are migrated depend on the version of GitLab you use on the destination. To determine if a
 specific group item is migrated:
@@ -304,14 +302,14 @@ Group items that are migrated to the destination GitLab instance include:
    - Already exists in the destination GitLab instance.
    - Has a public email in the source GitLab instance that matches a confirmed email in the destination GitLab instance.
 
-#### Excluded items
+### Excluded items
 
 Some group items are excluded from migration because they either:
 
 - May contain sensitive information: CI/CD variables, webhooks, and deploy tokens.
 - Are not supported: push rules.
 
-### Migrated project items **(BETA)**
+## Migrated project items **(BETA)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/267945) in GitLab 14.4 [with a flag](../../feature_flags.md) named `bulk_import_projects`. Disabled by default.
 > - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/339941) in GitLab 15.6.
@@ -384,7 +382,7 @@ Project items that are migrated to the destination GitLab instance include:
 </small>
 </html>
 
-#### Issue-related items
+### Issue-related items
 
 Issue-related project items that are migrated to the destination GitLab instance include:
 
@@ -397,7 +395,7 @@ Issue-related project items that are migrated to the destination GitLab instance
 | Merge request URL references    | [GitLab 15.6](https://gitlab.com/gitlab-org/gitlab/-/issues/267947)        |
 | Time tracking                   | [GitLab 14.4](https://gitlab.com/gitlab-org/gitlab/-/issues/267946)        |
 
-#### Merge request-related items
+### Merge request-related items
 
 Merge request-related project items that are migrated to the destination GitLab instance include:
 
@@ -411,7 +409,7 @@ Merge request-related project items that are migrated to the destination GitLab
 | Issue URL references                    | [GitLab 15.6](https://gitlab.com/gitlab-org/gitlab/-/issues/267947) |
 | Time tracking                           | [GitLab 14.5](https://gitlab.com/gitlab-org/gitlab/-/issues/339403) |
 
-#### Setting-related items
+### Setting-related items
 
 Setting-related project items that are migrated to the destination GitLab instance include:
 
@@ -422,7 +420,7 @@ Setting-related project items that are migrated to the destination GitLab instan
 | Project properties           | [GitLab 14.6](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75898) |
 | Service Desk                 | [GitLab 14.6](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75653) |
 
-#### Excluded items
+### Excluded items
 
 Some project items are excluded from migration because they either:
 
@@ -443,7 +441,7 @@ Some project items are excluded from migration because they either:
   - Pages domains
   - Remote mirrors
 
-### Troubleshooting
+## Troubleshooting
 
 In a [rails console session](../../../administration/operations/rails_console.md#starting-a-rails-console-session),
 you can find the failure or error messages for the group import attempt using:
@@ -468,7 +466,7 @@ entities.where(status: [-1]).pluck(:destination_name, :destination_namespace, :s
 You can also see all migrated entities with any failures related to them using an
 [API endpoint](../../../api/bulk_imports.md#list-all-group-or-project-migrations-entities).
 
-#### Stale imports
+### Stale imports
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352985) in GitLab 14.10.
 
@@ -483,7 +481,7 @@ import = BulkImports::Entity.where(namespace_id: Group.id).map(&:bulk_import)
 import.status #=> 3 means that the import timed out.
 ```
 
-#### Error: `404 Group Not Found`
+### Error: `404 Group Not Found`
 
 If you attempt to import a group that has a path comprised of only numbers (for example, `5000`), GitLab attempts to
 find the group by ID instead of the path. This causes a `404 Group Not Found` error in GitLab 15.4 and earlier.
@@ -499,7 +497,7 @@ To solve this, you must change the source group path to include a non-numerical
 
 - The [Groups API](../../../api/groups.md#update-group).
 
-#### Other `404` errors
+### Other `404` errors
 
 You can receive other `404` errors when importing a group, for example:
 
@@ -511,7 +509,7 @@ You can receive other `404` errors when importing a group, for example:
 This error indicates a problem transferring from the _source_ instance. To solve this, check that you have met the [prerequisites](#prerequisites) on the source
 instance.
 
-#### Reducing migration duration
+### Reducing migration duration
 
 A single direct transfer migration runs 5 entities (groups or projects) per import at a time, independent of the number of workers available on the destination instance.
 That said, having more workers on the destination instance speeds up migration by decreasing the time it takes to import each entity.
@@ -529,157 +527,6 @@ Distributing projects in different groups helps to avoid timeouts. If several la
 
 The GitLab UI can only migrate top-level groups. Using the API, you can also migrate subgroups.
 
-## Migrate groups by uploading an export file (deprecated)
-
-> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2888) in GitLab 13.0 as an experimental feature. May change in future releases.
-> - [Deprecated](https://gitlab.com/groups/gitlab-org/-/epics/4619) in GitLab 14.6.
-
-WARNING:
-This feature was [deprecated](https://gitlab.com/groups/gitlab-org/-/epics/4619) in GitLab 14.6 and replaced by
-[migrating groups by direct transfer](#migrate-groups-by-direct-transfer-recommended). However, this feature is still recommended for migrating groups between
-offline systems. To follow progress on an alternative solution for [offline environments](../../application_security/offline_deployments/index.md), see
-[the relevant epic](https://gitlab.com/groups/gitlab-org/-/epics/8985).
-
-Prerequisites:
-
-- Owner role on the group to migrate.
-
-Using file exports, you can:
-
-- Export any group to a file and upload that file to another GitLab instance or to another location on the same instance.
-- Use either the GitLab UI or the [API](../../../api/group_import_export.md).
-- Migrate groups one by one, then export and import each project for the groups one by one.
-
-GitLab maps user contributions correctly when an admin access token is used to perform the import. GitLab does not map
-user contributions correctly when you are importing from a self-managed instance to GitLab.com. Correct mapping of user
-contributions when importing from a self-managed instance to GitLab.com can be preserved with paid involvement of
-Professional Services team.
-
-Note the following:
-
-- Exports are stored in a temporary directory and are deleted every 24 hours by a specific worker.
-- To preserve group-level relationships from imported projects, export and import groups first so that projects can
-  be imported into the desired group structure.
-- Imported groups are given a `private` visibility level, unless imported into a parent group.
-- If imported into a parent group, a subgroup inherits the same level of visibility unless otherwise restricted.
-- You can export groups from the [Community Edition to the Enterprise Edition](https://about.gitlab.com/install/ce-or-ee/)
-  and vice versa. The Enterprise Edition retains some group data that isn't part of the Community Edition. If you're
-  exporting a group from the Enterprise Edition to the Community Edition, you may lose this data. For more information,
-  see [downgrading from EE to CE](../../../index.md).
-
-### Compatibility
-
-> Support for JSON-formatted project file exports [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/383682) in GitLab 15.8.
-
-Group file exports are in NDJSON format.
-
-You can import group file exports that were exported from a version of GitLab up to two
-[minor](../../../policy/maintenance.md#versioning) versions behind, which is similar to our process for
-[security releases](../../../policy/maintenance.md#security-releases).
-
-For example:
-
-| Destination version | Compatible source versions |
-|:--------------------|:---------------------------|
-| 13.0                | 13.0, 12.10, 12.9          |
-| 13.1                | 13.1, 13.0, 12.10          |
-
-### Exported contents
-
-The [`import_export.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/import_export/group/import_export.yml)
-file for groups lists items exported and imported when migrating groups using file exports. View this file in the branch
-for your version of GitLab to check which items can be imported to the destination GitLab instance. For example,
-[`import_export.yml` on the `14-10-stable-ee` branch](https://gitlab.com/gitlab-org/gitlab/-/blob/14-10-stable-ee/lib/gitlab/import_export/group/import_export.yml).
-
-Group items that are exported include:
-
-- Milestones
-- Group Labels (_without_ associated label priorities)
-- Boards and Board Lists
-- Badges
-- Subgroups (including all the aforementioned data)
-- Epics
-  - Epic resource state events ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/291983) in GitLab 15.4)
-- Events
-- [Wikis](../../project/wiki/group.md)
-  ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53247) in GitLab 13.9)
-- Iterations cadences ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95372) in 15.4)
-
-Items that are **not** exported include:
-
-- Projects
-- Runner tokens
-- SAML discovery tokens
-
-### Preparation
-
-- To preserve the member list and their respective permissions on imported groups, review the users in these groups. Make
-sure these users exist before importing the desired groups.
-- Users must set a public email in the source GitLab instance that matches their confirmed primary email in the destination GitLab instance. Most users receive an email asking them to confirm their email address.
-
-### Enable export for a group
-
-Prerequisites:
-
-- You must have the Owner role for the group.
-
-To enable import and export for a group:
-
-1. On the left sidebar, at the bottom, select **Admin Area**.
-1. Select **Settings > General**.
-1. Expand **Visibility and access controls**.
-1. In the **Import sources** section, select the checkboxes for the sources you want.
-
-### Export a group
-
-Prerequisites:
-
-- You must have the Owner role for the group.
-
-To export the contents of a group:
-
-1. On the left sidebar, select **Search or go to** and find your group.
-1. Select **Settings > General**.
-1. In the **Advanced** section, select **Export group**.
-1. After the export is generated, you should receive an email with a link to the [exported contents](#exported-contents)
-   in a compressed tar archive, with contents in NDJSON format.
-1. Alternatively, you can download the export from the UI:
-
-   1. Return to your group's **Settings > General** page.
-   1. In the **Advanced** section, select **Download export**.
-      You can also generate a new file by selecting **Regenerate export**.
-
-You can also export a group [using the API](../../../api/group_import_export.md).
-
-### Import the group
-
-1. On the left sidebar, at the top, select **Create new** (**{plus}**) and **New subgroup**.
-1. Select the **import an existing group** link.
-1. Enter your group name.
-1. Accept or modify the associated group URL.
-1. Select **Choose file...**.
-1. Select the file that you exported in the [Export a group](#export-a-group) section.
-1. To begin importing, select **Import**.
-
-Your newly imported group page appears after the operation completes.
-
-NOTE:
-The maximum import file size can be set by the administrator, default is `0` (unlimited).
-As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the
-[Application settings API](../../../api/settings.md#change-application-settings) or the
-[Admin Area](../../../administration/settings/account_and_limit_settings.md).
-Default [modified](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50 MB to 0 in GitLab 13.8.
-
-### Rate limits
-
-To help avoid abuse, by default, users are rate limited to:
-
-| Request Type     | Limit                                    |
-| ---------------- | ---------------------------------------- |
-| Export           | 6 groups per minute                |
-| Download export  | 1 download per group per minute  |
-| Import           | 6 groups per minute                |
-
 ## Automate group and project import **(PREMIUM ALL)**
 
 For information on automating user, group, and project import API calls, see
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md
index 877db58b716865ac2a6d7cab70791aae6a19dd26..2d58b8db3d4d0254c225d6cfc5dbe08c1f2f082c 100644
--- a/doc/user/group/manage.md
+++ b/doc/user/group/manage.md
@@ -165,7 +165,7 @@ Transferring groups moves them from one place to another in the same GitLab inst
 - Convert a subgroup into a top-level group by transferring it out of its current group.
 
 If you need to copy a group to a different GitLab instance,
-[migrate the group by direct transfer](import/index.md#migrate-groups-by-direct-transfer-recommended).
+[migrate the group by direct transfer](import/index.md).
 
 When transferring groups, note:
 
diff --git a/doc/user/project/import/gitlab_com.md b/doc/user/project/import/gitlab_com.md
index e604d9d871b9dcc25c2f8934be5ebb8b829f0e08..135b51bf81a620d414427b6abe29f065fd7b53d9 100644
--- a/doc/user/project/import/gitlab_com.md
+++ b/doc/user/project/import/gitlab_com.md
@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 WARNING:
 The GitLab.com importer was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/108502) in GitLab 15.8
 and removed in GitLab 16.0. To import GitLab projects from GitLab.com to a self-managed GitLab instance use
-[migrating groups and projects by direct transfer](../../group/import/index.md#migrate-groups-by-direct-transfer-recommended).
+[migrating groups and projects by direct transfer](../../group/import/index.md).
 
 ## Related topics
 
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index efc74b7ee1e2a4ce9b109b414ebc48dcf0e1ebe6..8c9ba4087990886846698d66f49fd962a8dabc79 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -15,7 +15,7 @@ To bring existing projects to GitLab, or copy GitLab groups and projects to a di
 ## Migrate from GitLab to GitLab by using direct transfer
 
 The best way to migrate GitLab groups and projects between GitLab instances, or in the same GitLab instance, is
-[by using direct transfer](../../group/import/index.md#migrate-groups-by-direct-transfer-recommended).
+[by using direct transfer](../../group/import/index.md).
 
 You can also migrate GitLab projects by using a GitLab file export, which is a supported import source.
 
diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md
index fc9b24362e077b78acd169efc0c0a2f0f87aebf4..dea50ecc40879801262cdfaaeeb988bae99033d1 100644
--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -4,27 +4,31 @@ group: Import and Integrate
 info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
 ---
 
-# Migrating projects using file exports **(FREE ALL)**
+# Migrate projects and groups by using file exports **(FREE ALL)**
+
+You can migrate projects and groups by using file exports. However, using
+[direct transfer](../../group/import/index.md) is recommended if possible.
+
+## Migrate projects by uploading an export file
 
 Existing projects on any self-managed GitLab instance or GitLab.com can be exported to a file and
-then imported into another GitLab instance. You can also copy GitLab projects to another location with more automation by
-[migrating groups by direct transfer](../../group/import/index.md#migrate-groups-by-direct-transfer-recommended).
+then imported into another GitLab instance.
 
-## Preserving user contributions
+### Preserving user contributions
 
 Preserving user contribution depends on meeting the following requirements:
 
-### Migrating from GitLab self-managed to GitLab.com
+#### Migrating from GitLab self-managed to GitLab.com
 
 When migrating projects by using file exports, an administrator's access token is required for user contributions to map correctly.
 
 Therefore, user contributions never map correctly when importing file exports from a self-managed instance to GitLab.com. Instead, all GitLab user associations (such as
 comment author) are changed to the user importing the project. To preserve contribution history, do one of the following:
 
-- [Migrate by direct transfer](../../group/import/index.md#migrate-groups-by-direct-transfer-recommended).
+- [Migrate by direct transfer](../../group/import/index.md).
 - Consider paid GitLab [migration services](https://about.gitlab.com/services/migration/).
 
-### Migrating to GitLab self-managed
+#### Migrating to GitLab self-managed
 
 To ensure GitLab maps users and their contributions correctly:
 
@@ -43,7 +47,7 @@ That user becomes an author of merge requests created by other users. Supplement
 - Added for comments, merge request approvals, linked tasks, and items.
 - Not added for the merge request or issue creator, added or removed labels, and merged-by information.
 
-## Edit project export files
+### Edit project export files
 
 You can add or remove data from export files. For example, you can:
 
@@ -58,7 +62,7 @@ To edit a project export file:
 
 You can also make sure that all members were exported by checking the `project_members.ndjson` file.
 
-## Compatibility
+### Compatibility
 
 > Support for JSON-formatted project file exports [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/389888) in GitLab 15.11.
 
@@ -75,7 +79,7 @@ For example:
 | 13.0                | 13.0, 12.10, 12.9          |
 | 13.1                | 13.1, 13.0, 12.10          |
 
-## Configure file exports as an import source **(FREE SELF)**
+### Configure file exports as an import source **(FREE SELF)**
 
 Before you can migrate projects on a self-managed GitLab instance using file exports, GitLab administrators must:
 
@@ -92,7 +96,7 @@ To enable file exports as an import source for the destination instance:
 1. Scroll to **Import sources**.
 1. Select the **GitLab export** checkbox.
 
-## Between CE and EE
+### Between CE and EE
 
 You can export projects from the [Community Edition to the Enterprise Edition](https://about.gitlab.com/install/ce-or-ee/)
 and vice versa, assuming [compatibility](#compatibility) is met.
@@ -101,7 +105,7 @@ If you're exporting a project from the Enterprise Edition to the Community Editi
 data that is retained only in the Enterprise Edition. For more information, see
 [downgrading from EE to CE](../../../index.md).
 
-## Export a project and its data
+### Export a project and its data
 
 Before you can import a project, you must export it.
 
@@ -124,7 +128,7 @@ To export a project and its data, follow these steps:
 The export is generated in your configured `shared_path`, a temporary shared directory, and then
 moved to your configured `uploads_directory`. Every 24 hours, a worker deletes these export files.
 
-### Items that are exported
+#### Items that are exported
 
 Exported project items depend on the version of GitLab you use. To determine if a
 specific project item is exported:
@@ -166,7 +170,7 @@ For a quick overview, items that are exported include:
 - Project and inherited group members, as long as the user has the Maintainer role in the
   exported project's group or is an administrator
 
-### Items that are not exported
+#### Items that are not exported
 
 Items that are **not** exported include:
 
@@ -189,7 +193,7 @@ Items that are **not** exported include:
 Migrating projects with file exports uses the same export and import mechanisms as creating projects from templates at the [group](../../group/custom_project_templates.md) and
 [instance](../../../administration/custom_project_templates.md) levels. Therefore, the list of exported items is the same.
 
-## Import a project and its data
+### Import a project and its data
 
 > Default maximum import file size [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50 MB to unlimited in GitLab 13.8. Administrators of self-managed instances can [set maximum import file size](#set-maximum-import-file-size). On GitLab.com, the value is [set to 5 GB](../../gitlab_com/index.md#account-and-limit-settings).
 
@@ -199,7 +203,7 @@ WARNING:
 Only import projects from sources you trust. If you import a project from an untrusted source, it
 may be possible for an attacker to steal your sensitive data.
 
-### Prerequisites
+#### Prerequisites
 
 > Requirement for Maintainer role instead of Developer role introduced in GitLab 16.0 and backported to GitLab 15.11.1 and GitLab 15.10.5.
 
@@ -209,7 +213,7 @@ may be possible for an attacker to steal your sensitive data.
 - Review [compatibility](#compatibility) for any issues.
 - At least the Maintainer role on the destination group to migrate to.
 
-### Import a project
+#### Import a project
 
 To import a project:
 
@@ -222,7 +226,7 @@ To import a project:
 To get the status of an import, you can query it through the [API](../../../api/project_import_export.md#import-status).
 As described in the API documentation, the query may return an import error or exceptions.
 
-### Changes to imported items
+#### Changes to imported items
 
 Exported items are imported with the following changes:
 
@@ -235,11 +239,11 @@ Exported items are imported with the following changes:
 
 Deploy keys aren't imported. To use deploy keys, you must enable them in your imported project and update protected branches.
 
-### Import large projects **(FREE SELF)**
+#### Import large projects **(FREE SELF)**
 
 If you have a larger project, consider [using a Rake task](../../../administration/raketasks/project_import_export.md#import-large-projects).
 
-## Set maximum import file size **(FREE SELF)**
+### Set maximum import file size **(FREE SELF)**
 
 Administrators can set the maximum import file size one of two ways:
 
@@ -248,7 +252,7 @@ Administrators can set the maximum import file size one of two ways:
 
 The default is `0` (unlimited).
 
-## Rate limits
+### Rate limits
 
 To help avoid abuse, by default, users are rate limited to:
 
@@ -258,11 +262,161 @@ To help avoid abuse, by default, users are rate limited to:
 | Download export | 1 download per group per minute |
 | Import          | 6 projects per minute           |
 
+## Migrate groups by uploading an export file (deprecated)
+
+> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2888) in GitLab 13.0 as an experimental feature. May change in future releases.
+> - [Deprecated](https://gitlab.com/groups/gitlab-org/-/epics/4619) in GitLab 14.6.
+
+WARNING:
+This feature was [deprecated](https://gitlab.com/groups/gitlab-org/-/epics/4619) in GitLab 14.6 and replaced by
+[migrating groups by direct transfer](../../group/import/index.md). However, this feature is still recommended for migrating groups between
+offline systems. To follow progress on an alternative solution for [offline environments](../../application_security/offline_deployments/index.md), see
+[the relevant epic](https://gitlab.com/groups/gitlab-org/-/epics/8985).
+
+Prerequisites:
+
+- Owner role on the group to migrate.
+
+Using file exports, you can:
+
+- Export any group to a file and upload that file to another GitLab instance or to another location on the same instance.
+- Use either the GitLab UI or the [API](../../../api/group_import_export.md).
+- Migrate groups one by one, then export and import each project for the groups one by one.
+
+GitLab maps user contributions correctly when an admin access token is used to perform the import. GitLab does not map
+user contributions correctly when you are importing from a self-managed instance to GitLab.com. Correct mapping of user
+contributions when importing from a self-managed instance to GitLab.com can be preserved with paid involvement of
+Professional Services team.
+
+Note the following:
+
+- Exports are stored in a temporary directory and are deleted every 24 hours by a specific worker.
+- To preserve group-level relationships from imported projects, export and import groups first so that projects can
+  be imported into the desired group structure.
+- Imported groups are given a `private` visibility level, unless imported into a parent group.
+- If imported into a parent group, a subgroup inherits the same level of visibility unless otherwise restricted.
+- You can export groups from the [Community Edition to the Enterprise Edition](https://about.gitlab.com/install/ce-or-ee/)
+  and vice versa. The Enterprise Edition retains some group data that isn't part of the Community Edition. If you're
+  exporting a group from the Enterprise Edition to the Community Edition, you may lose this data. For more information,
+  see [downgrading from EE to CE](../../../index.md).
+
+### Compatibility
+
+> Support for JSON-formatted project file exports [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/383682) in GitLab 15.8.
+
+Group file exports are in NDJSON format.
+
+You can import group file exports that were exported from a version of GitLab up to two
+[minor](../../../policy/maintenance.md#versioning) versions behind, which is similar to our process for
+[security releases](../../../policy/maintenance.md#security-releases).
+
+For example:
+
+| Destination version | Compatible source versions |
+|:--------------------|:---------------------------|
+| 13.0                | 13.0, 12.10, 12.9          |
+| 13.1                | 13.1, 13.0, 12.10          |
+
+### Exported contents
+
+The [`import_export.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/import_export/group/import_export.yml)
+file for groups lists items exported and imported when migrating groups using file exports. View this file in the branch
+for your version of GitLab to check which items can be imported to the destination GitLab instance. For example,
+[`import_export.yml` on the `14-10-stable-ee` branch](https://gitlab.com/gitlab-org/gitlab/-/blob/14-10-stable-ee/lib/gitlab/import_export/group/import_export.yml).
+
+Group items that are exported include:
+
+- Milestones
+- Group Labels (_without_ associated label priorities)
+- Boards and Board Lists
+- Badges
+- Subgroups (including all the aforementioned data)
+- Epics
+  - Epic resource state events ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/291983) in GitLab 15.4)
+- Events
+- [Wikis](../../project/wiki/group.md)
+  ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53247) in GitLab 13.9)
+- Iterations cadences ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95372) in 15.4)
+
+Items that are **not** exported include:
+
+- Projects
+- Runner tokens
+- SAML discovery tokens
+
+### Preparation
+
+- To preserve the member list and their respective permissions on imported groups, review the users in these groups. Make
+sure these users exist before importing the desired groups.
+- Users must set a public email in the source GitLab instance that matches their confirmed primary email in the destination GitLab instance. Most users receive an email asking them to confirm their email address.
+
+### Enable export for a group
+
+Prerequisites:
+
+- You must have the Owner role for the group.
+
+To enable import and export for a group:
+
+1. On the left sidebar, at the bottom, select **Admin Area**.
+1. Select **Settings > General**.
+1. Expand **Visibility and access controls**.
+1. In the **Import sources** section, select the checkboxes for the sources you want.
+
+### Export a group
+
+Prerequisites:
+
+- You must have the Owner role for the group.
+
+To export the contents of a group:
+
+1. On the left sidebar, select **Search or go to** and find your group.
+1. Select **Settings > General**.
+1. In the **Advanced** section, select **Export group**.
+1. After the export is generated, you should receive an email with a link to the [exported contents](#exported-contents)
+   in a compressed tar archive, with contents in NDJSON format.
+1. Alternatively, you can download the export from the UI:
+
+   1. Return to your group's **Settings > General** page.
+   1. In the **Advanced** section, select **Download export**.
+      You can also generate a new file by selecting **Regenerate export**.
+
+You can also export a group [using the API](../../../api/group_import_export.md).
+
+### Import the group
+
+1. On the left sidebar, at the top, select **Create new** (**{plus}**) and **New subgroup**.
+1. Select the **import an existing group** link.
+1. Enter your group name.
+1. Accept or modify the associated group URL.
+1. Select **Choose file...**.
+1. Select the file that you exported in the [Export a group](#export-a-group) section.
+1. To begin importing, select **Import**.
+
+Your newly imported group page appears after the operation completes.
+
+NOTE:
+The maximum import file size can be set by the administrator, default is `0` (unlimited).
+As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the
+[Application settings API](../../../api/settings.md#change-application-settings) or the
+[Admin Area](../../../administration/settings/account_and_limit_settings.md).
+Default [modified](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50 MB to 0 in GitLab 13.8.
+
+### Rate limits
+
+To help avoid abuse, by default, users are rate limited to:
+
+| Request Type     | Limit                                    |
+| ---------------- | ---------------------------------------- |
+| Export           | 6 groups per minute                |
+| Download export  | 1 download per group per minute  |
+| Import           | 6 groups per minute                |
+
 ## Related topics
 
 - [Project import and export API](../../../api/project_import_export.md)
 - [Project import and export administration Rake tasks](../../../administration/raketasks/project_import_export.md)
 - [Migrating GitLab groups](../../group/import/index.md)
 - [Group import and export API](../../../api/group_import_export.md)
-- [Migrate groups by direct transfer](../../group/import/index.md#migrate-groups-by-direct-transfer-recommended).
-- [Migrate groups by using file exports](../../group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated).
+- [Migrate groups by direct transfer](../../group/import/index.md).
diff --git a/doc/user/project/wiki/group.md b/doc/user/project/wiki/group.md
index 64f6fa2c75ebebc4b6f14e033d1eb303f998d9a0..59e949c5218a66c14bd55c9579cc373cff7e984a 100644
--- a/doc/user/project/wiki/group.md
+++ b/doc/user/project/wiki/group.md
@@ -37,7 +37,7 @@ To access a group wiki:
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53247) in GitLab 13.9.
 
 Users with the Owner role in a group can
-[import or export a group wiki](../../group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated) when they
+[import or export a group wiki](../../project/settings/import_export.md#migrate-groups-by-uploading-an-export-file-deprecated) when they
 import or export a group.
 
 Content created in a group wiki is not deleted when an account is downgraded or a
@@ -47,7 +47,7 @@ the wiki is exported.
 To access the group wiki data from the export file if the feature is no longer
 available, you have to:
 
-1. Extract the [export file tarball](../../group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated)
+1. Extract the [export file tarball](../../project/settings/import_export.md#migrate-groups-by-uploading-an-export-file-deprecated)
    with this command, replacing `FILENAME` with your file's name:
    `tar -xvzf FILENAME.tar.gz`
 1. Browse to the `repositories` directory. This directory contains a