mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
mintlify[bot]
b2433eac55
* docs: tighten long sentence in enterprise migration page * docs: tighten passive voice and long sentence in deslop docs * Apply suggestions from code review Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
87 lines
4.0 KiB
Plaintext
87 lines
4.0 KiB
Plaintext
---
|
|
title: "Enterprise migrations"
|
|
description: "Learn about the full-service enterprise migration process, including dedicated project management, delivery timelines, and QA review stages."
|
|
---
|
|
|
|
## Migration process
|
|
|
|
The migration process is highly collaborative and guided end-to-end by the Mintlify team. We work closely with your team to ensure you have a strong foundation to start on Mintlify.
|
|
|
|
<Steps>
|
|
<Step title="Scoping">
|
|
Submit the [migration form](https://mintlify.typeform.com/ent-migrations) with your documentation source, brand assets (logos, color codes, fonts), OpenAPI specs, and go-live date.
|
|
|
|
We lead a kick-off call to gather your content and determine your information architecture, then provide an estimated delivery timeline. We'll flag any areas of your migration that need discussion.
|
|
</Step>
|
|
|
|
<Step title="Content port-over">
|
|
We assemble your content into a Mintlify site, perform quality assurance on the content, and share a preview link so you can monitor progress in real time.
|
|
</Step>
|
|
|
|
<Step title="Feedback window (seven business days)">
|
|
Review the content port-over and submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe.
|
|
</Step>
|
|
|
|
<Step title="Set up your dashboard">
|
|
We deliver your migrated content as a zip file. Add the zip of content to your repository and make any content touch-ups with your team. Use the [go-live checklist](/migration-services/go-live-checklist) to set up your dashboard.
|
|
</Step>
|
|
|
|
<Step title="Go live">
|
|
Attach your [custom domain](/customize/custom-domain) to launch your documentation.
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Quality assurance
|
|
|
|
We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for:
|
|
|
|
<Card title="Content completeness" icon="file-check">
|
|
- All documentation from your source appears in your new docs.
|
|
- Content is properly formatted with Mintlify components.
|
|
- Navigation structure matches your specifications.
|
|
</Card>
|
|
|
|
<Card title="Visual elements" icon="palette">
|
|
- Images and videos display correctly.
|
|
- Custom fonts apply throughout.
|
|
- Light and dark mode logos display appropriately.
|
|
- Color schemes meet contrast requirements in both modes.
|
|
</Card>
|
|
|
|
<Card title="Functionality" icon="rocket">
|
|
- All links work correctly (no broken links).
|
|
- Table of contents renders properly.
|
|
- React components function as expected.
|
|
- No performance issues.
|
|
</Card>
|
|
|
|
<Note>
|
|
**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).
|
|
</Note>
|
|
|
|
## Frequently asked questions
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="How long does a migration take?">
|
|
We typically deliver migrations within 2-6 weeks, depending on complexity. You'll receive a specific timeline after the kick-off call.
|
|
</Accordion>
|
|
|
|
<Accordion title="Can I request changes after delivery?">
|
|
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.
|
|
</Accordion>
|
|
|
|
<Accordion title="What do I need to do after the migration is complete?">
|
|
The [go-live checklist](/migration-services/go-live-checklist) walks you through each of these steps, and we provide support along the way.
|
|
</Accordion>
|
|
|
|
<Accordion title="Can I customize the navigation structure?">
|
|
Yes. You can provide a custom information architecture and we implement it for you.
|
|
</Accordion>
|
|
|
|
<Accordion title="What happens if my documentation changes during the migration?">
|
|
Since migrations require a code freeze, any changes made to your source documentation after submission won't carry over. Complete all updates before starting the migration.
|
|
|
|
If a code freeze is not possible, our team works with you to run short sprints on specific sections. We can also reserve time after the first sprint to migrate any changes you make during the migration.
|
|
</Accordion>
|
|
</AccordionGroup>
|