diff --git a/astro/src/content/docs/lifecycle/migrate-users/provider-specific/pingone.mdx b/astro/src/content/docs/lifecycle/migrate-users/provider-specific/pingone.mdx
index 710189ae04..37af6a9a0e 100644
--- a/astro/src/content/docs/lifecycle/migrate-users/provider-specific/pingone.mdx
+++ b/astro/src/content/docs/lifecycle/migrate-users/provider-specific/pingone.mdx
@@ -41,7 +41,7 @@ Alternatively, you can do a bulk migration and force everyone to reset their pas
 
 ## Prerequisites
 
-This guide assumes you already have FusionAuth installed. If not, please [view our installation guides](/docs/get-started/download-and-install) and install FusionAuth before you begin. For more general migration information, please view the [general migration guide](/docs/lifecycle/migrate-users/provider-specific/general).
+This guide assumes you already have FusionAuth installed. If not, please [view our installation guides](/docs/get-started/download-and-install) and install FusionAuth before you begin. For more general migration information, please view the [general migration guide](/docs/lifecycle/migrate-users/general-migration).
 
 ## Planning Considerations
 
@@ -51,7 +51,7 @@ To preserve your users' passwords, you need to perform a slow migration. Users l
 
 If, on the other hand, resetting user passwords is acceptable, a <ScrollRef target="Bulk Migration" /> can work for you. Review that section for more details on the required steps. You may also perform a bulk migration after a slow migration has run for a while. Active users can be transparently migrated and infrequent users may not mind resetting their password.
 
-You can learn more about the types of migrations that FusionAuth supports [here](/docs/lifecycle/migrate-users/provider-specific/general#types-of-migrations).
+You can learn more about the types of migrations that FusionAuth supports [here](/docs/lifecycle/migrate-users/general-migration#types-of-migrations).
 
 ### Mapping User Attributes
 
@@ -539,7 +539,7 @@ When using a slow migration, you can estimate how many accounts will be migrated
 
 After this period, you may want to bulk migrate the rest of the users, or treat them as inactive and not migrate them. Plan to disable the Connector and remove the tenant's Connector Policy after the slow migration is complete.
 
-Learn more about [general slow migration considerations](/docs/lifecycle/migrate-users/provider-specific/general#slow-migration-implementation).
+Learn more about [general slow migration considerations](/docs/lifecycle/migrate-users/general-migration#slow-migration-implementation).
 
 ## Bulk Migration
 
diff --git a/src/redirects.json b/src/redirects.json
index 052d6539e9..406730299c 100644
--- a/src/redirects.json
+++ b/src/redirects.json
@@ -539,7 +539,6 @@
     "/docs/lifecycle/manage-users/search/": true,
     "/docs/lifecycle/manage-users/verification/": true,
     "/docs/lifecycle/migrate-users/": true,
-    "/docs/lifecycle/migrate-users/bulk/": true,
     "/docs/lifecycle/migrate-users/provider-specific/": true,
     "/docs/lifecycle/migrate-users/connectors/": true,
     "/docs/lifecycle/migrate-users/scim/": true,