Migration sucks. We know. That’s why we made it painless.
About ten minutes, start to finish. Every URL you have today still resolves tomorrow, your images and attachments come along, and your inbox, chat and ticketing don’t move at all.
- Every URL preserved
- Your support tool stays put
- Nothing publishes without you
You’ve stayed put for good reasons.
Every one of them has an answer. Read them before you decide.
“It’ll take forever.”
One click, and the import itself runs in a minute or two. Ten minutes covers the whole thing, domain included. Nobody on the team copy-pastes anything.
“We’ll lose our rankings.”
Original paths are preserved and 301 redirects are created for anything that changes. Sitemap and canonical tags are handled, so search engines follow you across.
“Every link we’ve ever sent will break.”
Old paths keep resolving, and internal links inside your articles are rewritten to point at the imported versions. Saved replies, onboarding emails and in-app links keep working.
“Our images and attachments won’t come.”
Images and file attachments come across with the article and are rehosted here, so nothing keeps loading from a tool you have stopped paying for.
“We can’t change our support tool.”
You don’t. Your inbox, chat and ticketing do not move at all. Ferndesk replaces the help center, and Fern keeps reading resolved tickets from the tool you already use.
“We’ll lose our structure.”
Collections, sub-collections and article order are mapped across as they are. You prune anything you do not want before you publish.
“Something will go live before we’ve read it.”
Nothing publishes without you. Everything lands as drafts against your structure, with a list of exactly what came in. Approve, edit or remove.
“We’ll be locked in all over again.”
Export the whole help center as markdown in a zip, or pull every article through the API, any time. You are never locked in.
If your docs have a URL, they can be here by lunchtime.
Paste the address. Fern reads your help center the way your customers do, page by page, and brings all of it across.
Intercom
Zendesk
Crisp
Help Scout
HubSpot
GitBook
Document360
Mintlify
- Notion
- HelpKit
- Freshdesk
- Docusaurus
- ReadMe
- Archbee
- Helpjuice
- KnowledgeOwl
- Stonly
- Zoho Desk
- ProProfs
- HelpDocs
- Slite
- Confluence
Any public URL
Paste the address of your help center and Fern crawls it: articles, collections, images and the links between them. If it isn’t listed above, it is almost certainly still importable.
Behind a login?
Private documentation moves too. Export it and it is live within a business day, or a Ferndesk engineer does the import for you, free. Same redirects, same review.
Ten minutes, three steps.
These are the same three screens you see when you sign up: paste your help center’s address, check what Fern imported, and point your domain at it.
Connect the old help center.
Paste the URL. Fern recognises the platform and pulls the articles, collections, images and redirects across.
Review the import.
Everything lands as drafts, mapped to your structure, with every URL preserved so nothing 404s. You read the list before a single article is public.
Point your domain.
Switch DNS to help.yourcompany.com, or drop the help center under yourcompany.com/help to keep the SEO on your main domain. The first verification run starts the same day.
The reason to switch isn’t the move. It’s what stops happening afterwards.
Any tool can store your articles. Fern keeps them true after every release.
Every article gets checked.
Fern tests each claim she can against your product: navigation steps, setting names, feature behaviour, screenshots, API shapes. Monthly on every plan, plus any time you click Verify. Anything she cannot check is flagged, not guessed.
New releases document themselves.
Pull requests are screened as they merge, so the article for a feature is drafted before the release goes out. The changes come back highlighted, and you approve them.
Answers your customers can trust.
The same verified articles power search, AI answers and the in-product widget. Deflection stops decaying every time you ship, because the content underneath it no longer rots.
Three teams that moved, in their own words.
“Not only was it super easy to migrate my old helpdesk, now my help center is so much more beautiful and easy to update.”
Fed Founder, GummySearch Case study →“We migrated from Zendesk Guide, and it feels like upgrading from internet of the 90s. Faster, no paid add-ons, and our knowledge base lives at a subfolder of our domain.”
Juan Founder, Duplika “We were trying to build it ourselves, trying to get the Crisp API working on our side and develop our own Ferndesk. We would be miles away from getting this into a working product.”
Jose Julio Chief Customer Officer, Metricool Case study →Everything people ask before they move.
If your question isn’t here, write to [email protected]. A human answers, and it’s usually the person who built the importer.
No. Original paths are preserved and 301 redirects are created for anything that changes. Sitemap and canonical tags are handled, so the rankings you have built keep pointing at the right article.
Your docs have been stale for months. Fix them in ten minutes.
Import your help center and Fern checks every article against your product, drafts the fixes, and keeps them current from then on. You approve, she publishes.
- 7-day free trial, no card
- Import in 10 minutes, URLs preserved
- Your support tool stays where it is
- Nothing publishes without you