Migration
Move your help desk over in one click
NiroHelp imports from seven other plugins. It runs in the background, it's safe to run twice, and your old plugin keeps its data until you decide to clean it up.
Your old plugin keeps its data
The importer copies content into NiroHelp and leaves the original where it is. Awesome Support attachments are the one exception: they are re-attached to the new ticket.
Safe to run twice
Each imported item is marked, so a second run skips what already came across.
Clean up when you’re ready
Once you have checked an import, Clean deletes the old plugin’s copies — after asking. It is permanent, so take a backup first.
Runs in the background
Large libraries import in batches and pick up where they left off.
Four steps, about ten minutes
Keep your old plugin switched on while it runs — NiroHelp reads from it, and its Migrate button stays greyed out until it is detected.
Install NiroHelp
Add it from your WordPress dashboard and leave your current help desk plugin active.
Open the Migration tab
NiroHelp detects which supported plugins are installed and enables only those buttons.
Click Migrate
A progress panel shows what has been imported so far. You can leave the page.
Check and go live
Review your imported articles and tickets, then point your menus at the new pages.
What transfers, plugin by plugin
The seven sources differ, so here's the honest breakdown of each — including what doesn't come across.
BetterDocs
Comes across
Every article, its categories and its helpful votes, converted into NiroHelp docs and topics.
Stays behind
Doc tags, BetterDocs layout settings and the rest of its analytics.
weDocs
Comes across
Articles, votes and the nested page hierarchy — parent pages become topics, leaf pages become docs.
Stays behind
The intro text on section pages, section order and weDocs tags.
Echo Knowledge Base
Comes across
Articles and categories from every knowledge base, merged into one set of topics.
Stays behind
Echo KB layouts, its article ordering and the split between knowledge bases.
BasePress
Comes across
Articles, votes, and knowledge bases and sections, mapped to docs and topics.
Stays behind
BasePress themes and its own article and section ordering.
Awesome Support
Comes across
Tickets, every reply, attachments, the assigned agent, and your product and department terms.
Stays behind
Priorities, private notes, ticket history and custom fields.
SupportCandy
Comes across
Tickets, threads, categories and assigned agents.
Stays behind
Priorities, tags, custom fields, guest accounts and copies of attachment files.
JS Help Desk
Comes across
Tickets, replies, departments and products.
Stays behind
Priorities, help topics, custom fields, internal notes and copies of attachment files.
What you get that your old plugin didn't have
Docs plugins and ticket plugins each solve half the problem. This is the other half.
| NiroHelp | Docs plugins | Ticket plugins | |
|---|---|---|---|
| Help articles for customers | Included — NiroHelp | Included — Docs plugins | Not included — Ticket plugins |
| Support ticket tracking | Included — NiroHelp | Not included — Docs plugins | Included — Ticket plugins |
| AI chat that answers from your docs | Included — NiroHelp | Not included — Docs plugins | Not included — Ticket plugins |
| AI that replies to tickets on its own | Included — NiroHelp | Not included — Docs plugins | Not included — Ticket plugins |
| Shared product taxonomy across both | Included — NiroHelp | Not included — Docs plugins | Not included — Ticket plugins |
| One admin menu, one settings screen | Included — NiroHelp | Not applicable — Docs plugins | Not applicable — Ticket plugins |
| Email intake for tickets | Included — NiroHelp | Not included — Docs plugins | Sometimes included — Ticket plugins |
Help articles for customers
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Included — Docs plugins
- Ticket plugins
- Not included — Ticket plugins
Support ticket tracking
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not included — Docs plugins
- Ticket plugins
- Included — Ticket plugins
AI chat that answers from your docs
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not included — Docs plugins
- Ticket plugins
- Not included — Ticket plugins
AI that replies to tickets on its own
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not included — Docs plugins
- Ticket plugins
- Not included — Ticket plugins
Shared product taxonomy across both
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not included — Docs plugins
- Ticket plugins
- Not included — Ticket plugins
One admin menu, one settings screen
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not applicable — Docs plugins
- Ticket plugins
- Not applicable — Ticket plugins
Email intake for tickets
- NiroHelp
- Included — NiroHelp
- Docs plugins
- Not included — Docs plugins
- Ticket plugins
- Sometimes included — Ticket plugins
After the import
Three things worth doing once your content has landed.
Check your article URLs
Pick the URL structure closest to your old one, then set up redirects for anything that changed.
Run a Sync if you use the AI
That pushes your freshly imported articles into the AI index so the chatbot can answer from them.
Expect thin history at first
Your ticket history comes across, but the day-by-day activity behind it does not — reports fill in from here.
Try the import on a staging site first
It's free, it's safe to run twice, and your current plugin keeps running the whole time.