From 18efa25095095e1cba7eee3f07cb703d6d898437 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 20 Nov 2025 20:41:22 +0000 Subject: [PATCH 1/3] Update migration-services/custom.mdx --- migration-services/custom.mdx | 128 ++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 migration-services/custom.mdx diff --git a/migration-services/custom.mdx b/migration-services/custom.mdx new file mode 100644 index 000000000..fce845c36 --- /dev/null +++ b/migration-services/custom.mdx @@ -0,0 +1,128 @@ +--- +title: Custom plan migrations +description: Overview of the full-service migration process, delivery timelines, and our quality assurance approach for Custom plans +--- + +You can choose to opt-for our migration services to transfer your documentation to Mintlify. This guide covers the migration process, delivery timelines, and our quality assurance approach. + +## What to expect for your migration + +A migration is a point-in-time transfer of your documentation that requires a code freeze. We migrate your documentation, API reference pages, branding (logos, colors, and fonts), and navigation structure. + +Your migration includes a staging link to review progress and a 7-day feedback window after delivery to address any issues with content, assets, or branding. + + +For Custom plans, migration services **also** include: +- Design or information architecture consultation +- Custom component development (landing pages, custom integrations, etc.) + + +## Migration process + +This is a highly collaborative process where we work closely with your team to implement custom solutions and builds that work for you! + + + +Submit the [migration form](https://mintlify.typeform.com/pro-migrations). + +Provide your documentation source, brand assets (logos, color codes, fonts), OpenAPI specs, go-live date, and preferred delivery method (GitHub PR or zip file). + + + +We review your submission and lead a kick-off call with our migration team to walk through your current set-up, understand any limitations and address any questions your team might have. + + + +We review and analyze the context from the call and provide an estimated delivery timeline within 24-48 hours. We'll flag any custom components or areas of your migration that need discussion. + + + +We start the migration and share a staging link so you can monitor progress in real-time. + + + +We deliver your migration via GitHub PR or zip file based on your preference. + + + +Submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe. + + + +We provide documentation and guidance for connecting your repository, setting up redirects, and configuring your custom domain. + + + +## Quality assurance + +We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for: + + +- All documentation from your source has been migrated. +- Content is properly formatted with Mintlify components. +- Navigation structure matches your specifications. + + + +- Images and videos display correctly. +- Custom fonts are applied throughout. +- Light and dark mode logos are used appropriately. +- Color schemes meet contrast requirements in both modes. + + + +- All links work correctly (no broken links). +- Table of contents renders properly. +- React components function as expected. +- No performance issues. + + +## After your migration + +Once we deliver your migration, you'll need to complete the following steps to launch your documentation: + +1. [Connect your GitHub repository and get setup](/quickstart#install-the-github-app). +2. [Set up redirects if required](/create/redirects). +3. [Configure your custom domain](/customize/custom-domain). +4. **Test before going live** - Before switching over from your old documentation: + - Review all pages on your staging link. + - Test navigation and search functionality. + - Verify all images and videos load correctly. + - Check that code blocks render properly. + - Test on mobile and desktop. +5. **Launch!** Your documentation is ready to go live! + + +**Need help?** Our migration team is available to guide you through these steps. Reach out via the dedicated slack channel or [support@mintlify.com](mailto:support@mintlify.com). + + +## Frequently asked questions + + + +We typically deliver migrations within 2-6 weeks, depending on complexity. You'll receive a specific timeline after the kick-off call. + + + +Yes. You have a 7-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe and work with you right until (outside of that window if required) you are ready to go live. + + + +The migration transfers your content, but you'll need to: +- Connect your documentation repository to your Mintlify dashboard. +- Set up redirects from your old documentation URLs. +- Configure your custom domain. + +We provide step-by-step documentation and support for each of these steps. + + + +Yes. You can provide a custom information architecture and we will implement it. We will also work with you on custom component development if that is needed and supported by the platform. + + + +Since migrations require a code freeze, any changes made to your source documentation after submission won't be included. We recommend completing all updates before starting the migration. + +If this is not possible, our team will work with you to set short sprints to migrate certain sections or reserve dedicated time post the first sprint to migrate the delta changes made during the migration. + + From 854c37a0fc352bf6e60eaa8324b9676cb1be57cb Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 21 Nov 2025 09:15:46 -0800 Subject: [PATCH 2/3] consolidate what to expect section --- migration-services/custom.mdx | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/migration-services/custom.mdx b/migration-services/custom.mdx index fce845c36..3c820ef56 100644 --- a/migration-services/custom.mdx +++ b/migration-services/custom.mdx @@ -1,22 +1,16 @@ --- -title: Custom plan migrations -description: Overview of the full-service migration process, delivery timelines, and our quality assurance approach for Custom plans +title: "Custom plan migrations" +description: "Overview of the full-service migration process, delivery timelines, and our quality assurance approach for Custom plans." --- -You can choose to opt-for our migration services to transfer your documentation to Mintlify. This guide covers the migration process, delivery timelines, and our quality assurance approach. +You can choose our migration services to transfer your documentation to Mintlify. This guide covers the migration process, delivery timelines, and our quality assurance approach. ## What to expect for your migration -A migration is a point-in-time transfer of your documentation that requires a code freeze. We migrate your documentation, API reference pages, branding (logos, colors, and fonts), and navigation structure. +A migration is a point-in-time transfer of your documentation that requires a code freeze. We migrate your documentation, API reference pages, branding (logos, colors, and fonts), and navigation structure. Migration services also include design or information architecture consultation and custom component development such as landing pages or custom integrations. Your migration includes a staging link to review progress and a 7-day feedback window after delivery to address any issues with content, assets, or branding. - -For Custom plans, migration services **also** include: -- Design or information architecture consultation -- Custom component development (landing pages, custom integrations, etc.) - - ## Migration process This is a highly collaborative process where we work closely with your team to implement custom solutions and builds that work for you! From cc9883214e16d4ef8f2d60964a3367cd3506a2c1 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 21 Nov 2025 10:26:29 -0800 Subject: [PATCH 3/3] copyedit --- migration-services/custom.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/migration-services/custom.mdx b/migration-services/custom.mdx index 3c820ef56..98149c1f3 100644 --- a/migration-services/custom.mdx +++ b/migration-services/custom.mdx @@ -13,7 +13,7 @@ Your migration includes a staging link to review progress and a 7-day feedback w ## Migration process -This is a highly collaborative process where we work closely with your team to implement custom solutions and builds that work for you! +The migration process is highly collaborative. We work closely with your team to implement custom solutions and builds that work for you! @@ -23,7 +23,7 @@ Provide your documentation source, brand assets (logos, color codes, fonts), Ope -We review your submission and lead a kick-off call with our migration team to walk through your current set-up, understand any limitations and address any questions your team might have. +We review your submission and lead a kick-off call with our migration team to walk through your current setup, understand any limitations, and address any questions your team might have. @@ -76,7 +76,7 @@ We work with vetted third-party vendors and conduct an internal quality audit be Once we deliver your migration, you'll need to complete the following steps to launch your documentation: 1. [Connect your GitHub repository and get setup](/quickstart#install-the-github-app). -2. [Set up redirects if required](/create/redirects). +2. [Set up redirects, if required](/create/redirects). 3. [Configure your custom domain](/customize/custom-domain). 4. **Test before going live** - Before switching over from your old documentation: - Review all pages on your staging link. @@ -87,7 +87,7 @@ Once we deliver your migration, you'll need to complete the following steps to l 5. **Launch!** Your documentation is ready to go live! -**Need help?** Our migration team is available to guide you through these steps. Reach out via the dedicated slack channel or [support@mintlify.com](mailto:support@mintlify.com). +**Need help?** Our migration team is available to guide you through these steps. Reach out via your dedicated Slack channel or [support@mintlify.com](mailto:support@mintlify.com). ## Frequently asked questions @@ -98,7 +98,7 @@ We typically deliver migrations within 2-6 weeks, depending on complexity. You'l -Yes. You have a 7-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe and work with you right until (outside of that window if required) you are ready to go live. +Yes. You have a 7-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe and work with you right until you are ready to go live. @@ -111,7 +111,7 @@ We provide step-by-step documentation and support for each of these steps. -Yes. You can provide a custom information architecture and we will implement it. We will also work with you on custom component development if that is needed and supported by the platform. +Yes. You can provide a custom information architecture and we will implement it. We also work with you on custom component development if that is needed and supported by the platform.