--- title: "Migrate to Document360" slug: "migrate-to-document360" description: "Migrating documentation from one knowledge base platform to another platform can be tricky and overwhelming. With Document360, it is just a simple process." tags: ["Content Migration", "Knowledge base", "SEO Preservation"] updated: 2026-07-24T11:13:14Z published: 2026-07-24T11:13:14Z canonical: "docs.document360.com/migrate-to-document360" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.document360.com/llms.txt > Use this file to discover all available pages before exploring further. # Migrate to Document360 Moving your existing documentation to Document360 is handled by our migration team; from content transfer and URL redirects to SEO preservation and quality checks. Submit a request and a dedicated migration expert will guide you through the entire process. --- ## What we migrate When you initiate a migration request, our team handles all of the following: - All articles and categories - Images and file attachments - Internal links and URL structures - Redirect rules to preserve SEO rankings - Landing page - Branding, custom CSS, and site customization - Metadata - authors and publish dates where available Supported platforms We can import your existing knowledge base from pretty much any platform. We've built internal tools to make this process seamless. Here are some of the platforms we've migrated customers from: Zendesk, Freshdesk, Confluence, Intercom, GitHub, WordPress, HelpDocs, Drift, HelpScout, Readme, Helpjuice, MadCap Flare, and more. --- ## How to initiate a migration request There are two ways to submit a migration request - pick the one that fits where you are: Use the website form Not signed up yet? No Document360 account needed. Fill out the migration request form on our website and a migration expert will reach out. [Go to migration request form →](https://document360.com/migration-request/#MigrationForm) Submit from the portal Already on a trial or paid plan? Initiate the request directly inside Document360, right from your project settings. [See steps below →](https://docs.document360.com/docs/migrating-documentation-from-another-knowledge-base-platform#to-submit-from-the-portal) --- ## To submit from the portal 1 Navigate to **Settings** in the left navigation bar. 2 Go to **Knowledge base portal** > **Migrate content**. 3 Click **Request migration**. A dialog box appears. 4 Enter the URL of your existing knowledge base in the **External knowledge base link** field. This is the URL where your content is currently live — for example, `docs.yourcompany.com` 5 Enter your current documentation platform in the **Current platform** field. For example: Zendesk, Intercom, Confluence, WordPress. 6 Click **Submit**. A migration expert will contact you within one business day. --- ## What happens next After you submit, here's how the migration process works: 1 ~1–2 days after submission Kick-off Your migration expert contacts you to understand your current setup, content volume, and any special requirements. They'll give you a specific timeline estimate and answer all questions before any work begins. 2 Typically 2–4 weeks Migration The team uses a combination of automated tools and manual processes to transfer your content into Document360. You'll receive regular updates throughout, with opportunities to review and give feedback at each stage. 3 Before go-live Test and go live The team performs a thorough quality check, sets up redirect rules, and confirms your new knowledge base is live, without losing any of the organic search traffic your existing documentation has built up. NOTE Larger migrations with complex URL structures or high content volumes may take longer. Your migration expert will give you a specific estimate during the kick-off call. --- ## Setting up redirect rules Your migration team handles redirect rules as part of the migration process. This section is here if you need to add or adjust redirects yourself after migration is complete. After migration, redirect rules forward your old URLs to their new Document360 equivalents, so that bookmarks, backlinks, and search engine rankings are all preserved. ### Why this matters When you move to a new platform, your old URLs stop working unless you tell the server where to send visitors. Without redirect rules, anyone who clicks a bookmarked article, follows a backlink, or lands on your docs through a Google search will hit a 404 error instead. This frustrates readers mid-task and causes search engines to eventually drop those pages from their index, erasing the organic rankings your documentation has built up over time. ### To set up a redirect rule 1 Go to **Settings** > **Knowledge base site** > **Article redirect rules** > **New redirect**. 2 Set the **Redirect type** to **Replace with**. 3 Enter your old subfolder path in the **Source path** field. 4 Enter the new path in the **Destination URL** field. 5 Click **Create**. Example To redirect all articles from `/help/customer/` to `/docs/en/` on `docs.yourcompany.com`: Source path `/help/customer/` Destination URL `/docs/en/` All URLs matching that subfolder pattern will automatically redirect to the new path. --- ## FAQ **Can I bring my existing content into Document360 myself, without submitting a migration request?** Yes. If you'd rather not wait on the migration team, you can import your own `.docx` or `.pdf` files directly from the Advanced WYSIWYG editor, either as a single article or split automatically into multiple articles by heading level, without using the migration support from the Document360 team. This is a good fit for smaller or one-off imports. For a full knowledge base move — with URL redirects, SEO preservation, and hands-on support — use the migration request process described above instead. See [Import from Word](https://docs.document360.com/docs/import-from-word) and [Import PDF](https://docs.document360.com/docs/import-pdf) for details. **How long does migration take?** Most migrations complete within **2–4 weeks**. Larger projects with high content volume or complex URL structures may take longer. Your migration expert will give you a specific estimate during the kick-off call, before any work begins. **What if something looks wrong after migration?** Contact [Document360 support](https://document360.com/support/) and reference your migration ticket number. The migration team handles post-migration issues as part of the service - just reach out and they'll resolve it. **Can you migrate from a platform not on the list?** Most likely, yes. The migration team has worked with a wide range of platforms beyond the ones listed. [Contact us](https://document360.com/migration-request/#MigrationForm) with your current platform name and a brief description of your setup, and the team will confirm if it's supported before you submit a formal request. ## Related - [Offline documentation](/offline-documentation.md) - [Import & Export project](/import-export.md) - [Import project ZIP file](/import-a-documentation-project.md)