EU, US and India data residency · a DPA you can sign

Trust Center →

ServiceDesk Plus to FlowTux: cloud or on-prem

ServiceDesk Plus ships as a cloud service and an on-prem install, and the export path is different for each. Work out which one you run before anything else.

Getting your data out of ManageEngine ServiceDesk Plus

Each line below was checked against ManageEngine ServiceDesk Plus’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.

UI export
Request list view: select requests > Actions > Export Requests. Available only in the list view, for technicians. Source: help.servicedeskplus.com
Reports
Custom request reports export as HTML, PDF, XLS, XLSX, CSV, DOC, DOCX or XML. Source: help.servicedeskplus.com
Cloud API
GET <domain>/app/<portal>/api/v3/requests with Zoho OAuth 2.0 (scopes like SDPOnDemand.requests.READ). Page with list_info row_count and start_index; has_more_rows tells you when to stop. Source: manageengine.com
Notes
GET .../api/v3/requests/{id}/notes. Each note has show_to_requester, which separates internal notes from visible ones. Source: manageengine.com
On-prem API
The v3 API authenticates with a technician’s API key (authtoken header), generated under Admin > Technicians. The key only sees what that technician’s role sees. Source: manageengine.com
On-prem backup
backUpData includes the database and attachments; trimmedBackupData is database only. Builds 11304 and later write password-protected .ezip files. Source: help.servicedeskplus.com
Attachments (cloud)
Release notes from August 2026: downloading more than 20 attachments one by one in a short period returns a Too Many Requests error. Source: manageengine.com
CMDB
Configuration items export from the CMDB list view as HTML, XLS, XLSX, PDF or CSV. Source: help.servicedeskplus.com

Not verified

We could not confirm these from ManageEngine ServiceDesk Plus’s documentation. Check them in your own account.

  • Formats and row limit of the request list Export dialog.
  • Whether a UI export includes notes, conversations or attachments.
  • The v3 endpoint for email conversations, and published API rate limits for cloud or on-prem.
  • A bulk export for solutions (knowledge base).

Field mapping

What each ManageEngine ServiceDesk Plus field becomes in FlowTux. We confirm every row with you before loading.

ManageEngine ServiceDesk PlusFlowTuxNotes
display_idOriginal ticket number, kept on the imported ticket
subject, descriptionTicket title and first message
statusStatus: Open, In Progress, Resolved, ClosedMap your status list on the call.
priority, urgency, impactPriority: Critical, High, Medium, LowUrgency and impact are kept as context.
category, subcategory, itemCategory, the starting taxonomy Tux AI triages againstThe three levels flatten into one category list.
request_typeRecorded on the ticketIncident vs service request.
requesterRequester, matched by email address
technician, groupOwner: an Admin or Agent member
site, departmentRecorded on the ticket
note (show_to_requester: true)Comment on the ticket thread
note (show_to_requester: false)Internal note, never shown to the requester
resolutionResolution note
udf_fieldsTicket body, or archiveFlowTux has no documented custom-field object. Values you need are written into the ticket during import; the rest stay in the archive. Agreed field by field on the scoping call.
worklogsNot carriedTime tracking stays in ServiceDesk Plus.
assets, configuration_itemsStay in ServiceDesk Plus

What carries over

  • Requests in the window you choose, with visible notes and internal notes kept apart
  • Status, priority and the category tree, mapped as in the table
  • Requesters and technicians, matched by email
  • Resolutions, as resolution notes

What does not

  • Assets, the CMDB, and the problem, change, release and project modules
  • Business rules, custom triggers and SLA definitions; targets are restated in FlowTux
  • Worklogs and time tracking
  • Approvals and the service catalog
  • Attachments on closed requests, unless you decide otherwise on the scoping call

The ManageEngine ServiceDesk Plus plan, step by step

  1. Confirm cloud or on-premCloud runs on a Zoho data-center domain (sdpondemand.manageengine.com and regional variants). On-prem runs on your own server and port.
  2. On-prem: export from a restored backupRun trimmedBackupData for a database-only copy, restore it on a staging server, and point the export there so production is untouched.
  3. Cloud: register an OAuth appIn the Zoho API console, with read scopes for requests. Page /api/v3/requests until has_more_rows is false, then pull notes per request.
  4. Bring attachments for open requests onlyCloud throttles one-by-one attachment downloads above 20 in a short period. Pulling files only for open requests keeps the export inside that.
  5. Send the export; we map itWe flatten category, subcategory and item with you, map statuses, and check counts per status and per month.
  6. Run both for two weeksRepoint the mailbox and Slack to FlowTux. Keep ServiceDesk Plus for assets and change, or read-only for history.

Run both. Decide with data.

The risk in switching helpdesks is not the import. It is committing before you know whether the AI actually closes your tickets. So keep ManageEngine ServiceDesk Plus running, send new tickets to FlowTux, and compare the two queues on live traffic for two weeks. If the numbers do not justify the move, you have lost two weeks and no data.

How long it takes

ManageEngine publishes no API rate limits, so throughput is something to measure on a test pull, not promise. The parallel run is two weeks.

Migration help is included: we do the import and the field mapping with you on a call, at no extra cost and on every plan. There is no self-serve importer, so nothing loads until you have seen the mapping.

ManageEngine ServiceDesk Plus migration FAQ

How do we export requests from ServiceDesk Plus?

From the request list view, select requests and use Actions > Export Requests. For full history including notes, use the v3 API on cloud, or work from a restored database backup on-prem.

Does the ServiceDesk Plus API work the same on cloud and on-prem?

No. Cloud uses Zoho OAuth 2.0 tokens and data-center specific domains. On-prem uses a technician API key in the authtoken header, limited to that technician’s role.

What happens to ServiceDesk Plus assets and CMDB?

They stay in ServiceDesk Plus. FlowTux runs the ticket queue and triage; it is not an asset database. Configuration items can be exported from the CMDB list view for your records.

Will internal notes stay internal?

Yes. Each note carries show_to_requester. Notes the requester could not see are imported as FlowTux internal notes.

Start with two weeks in parallel

Keep ManageEngine ServiceDesk Plus running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.