Docs-as-code migrations
Zendesk to Docusaurus migration
This is for SaaS support and docs teams whose help center runs on Zendesk Guide and whose articles have quietly become the product's real documentation. We move those articles into a Docusaurus site in your Git repository without breaking what already works: every article URL that ranks in search, sits in an agent macro or is linked from inside the product keeps landing on the right page.
From $4,500 (up to 150 pages), $9,500 (up to 500 pages), custom above
Reply within 1 business day
30-day fix window
Who it's for#who-its-for
- Heads of support who keep Zendesk for tickets but want the help center versioned, reviewed and owned by the company rather than rented.
- Docs leads who have hit the limits of Guide themes and want real navigation, reusable content and versioned documentation.
- Engineering leads who want in-product help links and API docs served from the same repository and build as the rest of the documentation.
- Growth and SEO owners whose help center brings in organic traffic they cannot afford to lose during a platform change.
Moving the help center does not mean leaving Zendesk. Tickets, macros and the agent workspace stay exactly where they are; only the published articles move, and the new site can still link to your Zendesk request form. It is also a good moment to clean up: help centers collect near-duplicate articles over time, and the inventory marks each one to keep, merge or retire before anything moves.
What you get#what-you-get
Search continuity is the reason this page exists, so most of the deliverables are about keeping every existing link alive:
- Every article, section and category exported through the Zendesk Help Center API, including any drafts you want to keep.
- Articles converted from Zendesk's HTML into clean MDX with frontmatter, each keeping its title and gaining a description written for search.
- A redirect map covering article URLs in every locale you publish, section and category pages, and the help center home.
- Permanent (301) redirects implemented at the server or edge rather than client-side refreshes, then tested against the full URL list.
- Internal links rewritten, plus a list of agent macros and in-product help links your team should update to the new URLs.
- A sitemap for the new site and a Google Search Console checklist to work through after launch.
- A navigation designed around your products, instead of Guide's fixed category, section and article hierarchy.
Before cutover, you get the full redirect map as a spreadsheet you can check line by line: the old URL, the new URL, and the reason for every mapping that is not a straight match.
How it runs#how-it-runs
- Scoping. We pull the article list from the API, count articles per locale, and send a fixed quote.
- Inventory and URL audit. We record every URL, what links to it and which pages earn search traffic, using your analytics or Search Console data if you share it.
- Conversion and structure. Articles are converted, merged where Zendesk accumulated duplicates, and placed in the new navigation. You review everything on a preview site.
- Redirects and cutover. If your help center is host-mapped to your own subdomain, that subdomain moves to the new site, which answers the old article paths with 301s. Otherwise, Zendesk's redirect rules can send old article URLs to the new site while the help center stays live. We test every redirect before and after the switch.
- 30-day fix window. For 30 days after delivery, we review crawl errors with you and fix any URL that slipped through, at no charge.
Zendesk article URLs carry a numeric ID followed by a slug, and older links often use a slug that has since changed. Wherever the host supports pattern matching, the redirect map keys on the ID, so every variant of an old link lands on the same new page.
Pricing#pricing
- Up to 150 pages
- From $4,500
- about €4,150
- Up to 500 pages
- From $9,500
- about €8,750
- Above 500 pages
- Custom quote
Help center migrations use the same page-count tiers as every migration, with translated articles counted as part of the total we agree during scoping. Articles we decide to retire do not count. Above 500 pages, we quote after reading a representative sample.
What moves the price: the number of locales; customized Guide themes whose markup leaked into article bodies; articles that embed videos or files hosted in Zendesk; and how much of the help center we agree to restructure rather than move as it is. A help center with clean articles in a single language sits at the easy end. The quote itemizes locales and restructuring, so you can see what each choice costs.
Prices are in US dollars; the euro figures are approximate conversions for reference. If the move is also a chance to fix what customers keep asking about, pair it with support-ticket mining so the new site launches with the missing articles already written.
Frequently asked questions#faq
Do we have to leave Zendesk?
Can we keep our help center subdomain?
What about community posts and the request form?
What happens to images and files attached to articles?
Send us what you have
Send a link to your docs, an export, or a few lines on what needs to change. We reply within 1 business day with questions or a quote.