New — the AI auto-responder now answers tickets on its own. See how it works

Switching from JS Help Desk to NiroHelp

Your tickets and replies move across in one click, with departments and products. Then add a knowledge base, and an AI that answers tickets from it — in the same plugin.

See the four steps

Free plan on WordPress.org · Importing never modifies JS Help Desk

The mapping

JS HELP DESKTickets
NIROHELPTickets
JS HELP DESKReplies
NIROHELPReplies
JS HELP DESKDepartments
NIROHELPReasons
JS HELP DESKProducts
NIROHELPProducts

What comes across

Every ticket
Subject, message and date, credited to the customer’s WordPress account where they have one.
Every reply
The conversation, in order, with each reply’s author name.
Departments
Each department becomes a ticket reason.
Products
JS Help Desk products become NiroHelp products.
Open and closed alike
Tickets are imported whatever state they are in.

What doesn't: Priorities, help topics, custom fields, internal notes and due dates stay behind. Attachments are not copied into your Media Library — each message lists its files by name and address, and the files stay in JS Help Desk’s upload folder. No accounts are created, so a guest’s ticket arrives without a customer attached, and staff assignments may not line up with your WordPress users.

Four steps, about ten minutes

Keep JS Help Desk activated while this runs — NiroHelp reads from it, and the Migrate button stays greyed out if it can't find it.

Install NiroHelp

Add it from your dashboard and activate it. Leave JS Help Desk switched on, and keep the AI auto-responder off until the import is done.

Open the Migration tab

NiroHelp → Settings → Migration. JS Help Desk shows up as detected, with its Migrate button enabled.

Click Migrate

It imports in batches in the background. A progress panel keeps count — you can close the tab.

Check and go live

Review the imported tickets, then link your menus to the My Tickets and Submit a Ticket pages.

Why it's safe to just try it

Run it on staging, or run it twice — the import never changes JS Help Desk. Deleting the old copies is a separate step you take when you're ready.

JS Help Desk is only read

The import only reads JS Help Desk's tables. Nothing in them is edited or deleted.

Safe to run twice

Already-imported tickets are marked and skipped on the next run.

Clean up when you’re ready

Once you've checked the import, Clean deletes JS Help Desk's copies — after asking — and keeps every NiroHelp copy.

Handles a long history

Imports in resumable batches, so years of tickets are fine.

What you add on top of your JS Help Desk tickets

Everything here is in NiroHelp today — check it against what your JS Help Desk setup does now.

Knowledge base with topics and search

NiroHelp
Included — NiroHelp
Plan
Free

Products shared by articles and tickets

NiroHelp
Included — NiroHelp
Plan
Free

Customer login by code, magic link or password

NiroHelp
Included — NiroHelp
Plan
Free

Random, round-robin or least-loaded assignment

NiroHelp
Included — NiroHelp
Plan
Free

Dashboard that flags tickets needing attention

NiroHelp
Included — NiroHelp
Plan
Free

AI chatbot that answers from your articles

NiroHelp
Included — NiroHelp
Plan
Pro

AI auto-responder for tickets

NiroHelp
Included — NiroHelp
Plan
Pro

Email piping from your mailbox

NiroHelp
Included — NiroHelp
Plan
Pro

Unlimited agents and unlimited tickets on every plan, including the free one.

After the import

Three things to check before customers sign in.

Review ticket statuses

Tickets with a conversation can arrive marked as waiting on your team. Filter the imported tickets and close the ones that were already finished.

Reassign open tickets

JS Help Desk keeps its own staff records, so the agent on an imported ticket may not be the right person. Check open tickets and reassign where needed.

Start your knowledge base

Write articles for the questions your old tickets keep asking, then run a Sync on Pro so the AI can answer from them.

FAQ

Questions about switching

No — the opposite. Leave JS Help Desk activated while the import runs, because NiroHelp reads directly from it. The Migrate button stays disabled until it detects JS Help Desk is present. Once the import is finished and you have checked the results, you can deactivate JS Help Desk whenever you like.

Try it on a staging copy first

Import your ticket history, look around, and decide. JS Help Desk keeps working the whole time.

All 7 migration sources