ManageEngine ServiceDesk Plus vs iTop: which to choose

Which fits a ServiceDesk Plus Enterprise team: iTop or staying put

iTop fits teams that want a customizable CMDB data model, graphical impact analysis and self-hosted control of their configuration data. ServiceDesk Plus fits teams that want a single vendor-packaged suite with its own support path and less internal build work. Before renewing, decide which of those two outcomes your Enterprise team actually needs, because the choice turns on four factors: how complex your data model is, how many agents you will run against Combodo's tiers, whether you have in-house PHP and MySQL or MariaDB skills, and how much extension work your team will accept.

Start with the data model. If your CMDB relationships are shallow and your change process mostly follows standard templates, the bundled ServiceDesk Plus modules may cover you with little configuration. If you rely on custom classes, multi-level dependencies and impact views that feed change approval, iTop's customizable model and graphical impact analysis are the stronger fit, but you will spend time designing and validating that model. Next, count your agents. Combodo's Community tier covers up to 10 agents, Atelier up to 50 and Forge more than 50, each available on premises or as SaaS, so confirm your agent count and growth with Combodo before choosing a deployment. Then check your staff. iTop runs on PHP 8.2 to 8.4 with MySQL or MariaDB, plus GraphViz, and someone must own upgrades and extension compatibility.

Ask Combodo and your ServiceDesk Plus reseller for a written comparison covering the specific CMDB classes, SLA rules and change workflows you use today, and list which ones need an iTop extension from the iTop Hub or custom integration. Budget for that work as a one-time cost, and confirm which support you will need afterward, because Combodo's commercial support is separate from any extension maintenance. If the gap list is short and your team can own PHP and database operations, a migration is worth planning. If the list is long or no one on staff can support the stack, staying on ServiceDesk Plus with a renewed scope may be the lower-risk path for now.

Which product fits which buyer situation

This table compares ServiceDesk Plus Enterprise and self-hosted iTop across six buyer situations, naming the better fit and the reason for each. Read each row against your own CMDB depth, approval model and agent count, and treat the conditions column as the point where either product could win.

Buyer situation	Better fit	Reason and conditions
Heavy custom CMDB relationships	iTop	iTop's CMDB is fully customizable and built around relationships between classes, with graphical impact analysis. Confirm that your ServiceDesk Plus CMDB model maps cleanly to iTop classes before choosing.
Change approval chains with multiple CAB stages	Either, leaning iTop	iTop covers change management with customizable workflows. ServiceDesk Plus Enterprise has mature change modules, so verify that each approval stage and notification you rely on can be rebuilt in iTop.
Small agent count (up to 10 technicians)	Either	iTop Community is free for up to 10 agents, and GLPI has no license fee at any size. Choose on module fit and team skills, not on licensing alone.
No internal PHP or database skills	ServiceDesk Plus or a managed iTop	iTop runs on PHP with MySQL or MariaDB and needs GraphViz. Without that skill set, budget for an implementation partner or Combodo support, or keep the commercial product.
Air-gapped or strictly on-premises deployment	iTop	iTop is self-hosted in your own infrastructure with no outbound dependency for core use. Confirm that required extensions and any update path work offline in your environment.
Existing ManageEngine integrations and asset scanning	ServiceDesk Plus, unless integrations are rebuilt	Native ManageEngine asset discovery and connectors will not carry over. iTop needs extensions or integration work, and inventory typically comes from a separate tool. Confirm each integration before planning the cutover.

How Combodo's agent tiers map to your team size

Combodo sizes iTop licenses by the number of agents who work in the tool, not by the number of technicians or assets. The Community edition is free for up to 10 agents, Atelier covers up to 50 agents and Forge covers more than 50. Each tier is available on premises or as SaaS. ServiceDesk Plus prices per technician across its Standard, Professional and Enterprise editions, so the same team can land in a different cost band under each product. Count the people who log in to resolve, approve or edit tickets and changes, then compare that number with the tier boundaries before you assume a free tier fits.

Agent counts do not map one to one onto technicians. Requesters who only raise tickets through a portal, and read-only viewers, may or may not count, depending on how Combodo defines an agent in its current terms. Shared service desk logins, contractors working through a managed service provider and staff in change advisory roles also need a clear answer. Ask Combodo to confirm in writing how each of these groups is counted, and whether a SaaS deployment changes the count or the commercial terms.

Ask Combodo what each tier includes beyond the agent limit. Confirm which features, support levels, training and consultancy options and hosting arrangements apply to Community, Atelier and Forge, and whether extensions from the iTop Hub carry their own licensing. Ask how growth is handled when your agent count crosses a tier boundary mid-contract. The answers determine the recurring cost of the platform, and they should sit beside the server and operations costs in your comparison. Treat the published tier names as a starting point and confirm current commercial terms directly with Combodo before you commit.

Where iTop needs extensions or integration work

iTop covers most of the CMDB, change and SLA ground that ServiceDesk Plus Enterprise customers rely on, but several areas usually need an extension from the iTop Hub, custom development or integration work. Each card below names what the area depends on and what to confirm before you commit to a scope.

ServiceDesk Plus connectors

Moving data in and out of ServiceDesk Plus is the first integration question, because the reports and exports you use today will not map one to one onto iTop objects. Confirm which ServiceDesk Plus data sets you need (requests, assets, relationships, change records) and whether iTop's CSV import and data synchronization cover each one. Any feed that runs during a parallel period, such as monitoring alerts or asset data, needs a named owner and a tested mapping before cutover.

Asset discovery

iTop manages configuration items well, but it does not replace a discovery agent by itself. If ServiceDesk Plus currently populates the CMDB from scans, you will need a discovery source such as a separate inventory tool, scripts or an integration that writes into iTop. Confirm which hosts, network devices and software records must be refreshed automatically and how stale items will be retired.

Reporting parity

Standard dashboards in iTop will not match every ServiceDesk Plus report one for one. Build an inventory of the reports your managers, auditors and change board actually read, then decide which are rebuilt in iTop, which move to an external BI tool and which are retired. Ask for a sample output of each critical report before accepting the new design.

SSO and directory sync

Single sign-on and user or group synchronization depend on your identity provider and on how iTop profiles map to your current ServiceDesk Plus roles. Confirm the authentication method you need, how technicians and requesters are provisioned and deprovisioned, and whether the approach requires an extension or custom code. Test offboarding as carefully as login.

Notifications and escalations

Email templates, escalation rules and notifications for SLA breaches are configurable in iTop, but a faithful copy of your ServiceDesk Plus workflow often needs custom triggers or an extension from the iTop Hub. List each automated message your teams depend on, including recipients and timing, and test them against real SLA clocks. Confirm mail server and relay settings early.

Change approval workflows

Multi-level change approvals, advisory boards and emergency change paths are where iTop customizations are most likely. Document your current approval chains, risk scoring and freeze windows, then confirm which ones iTop models natively and which need a custom lifecycle or extension. Plan for a review with your change manager before any build starts, since approvals are the control auditors will sample.

What hosting in your own infrastructure changes for data and compliance

Moving from ManageEngine ServiceDesk Plus to iTop changes who holds the ticket, CMDB and audit data, and who must prove it. The cards below cover where data sits, which hosting model you choose, how sign-in is wired, and what evidence an assessor will ask for. DeployOpen prepares controls and evidence for compliance assessments, but it does not issue audit reports or certifications; independent auditors and certification bodies do that work.

Data location and hosting model

iTop can run on premises, as SaaS from Combodo, or on your own cloud accounts or data centers. Each choice moves the database, attachments and CMDB records to a different party. With MySQL or MariaDB under iTop, the database sits in the tier you operate, so confirm in writing where backups and replicas land before you sign with any hosted option. Ask Combodo which region and sub-processors apply to its SaaS edition.

Database ownership and backups

Self-run iTop puts the MySQL or MariaDB instance, its patching and its backup schedule under your team. A ticket and CMDB export is only as good as the last restore you tested. Set a restore test that covers attachments and the CMDB together, and record the result as evidence. Teams that already run database operations usually find this the smallest change in the move.

Identity and sign-in integration

ServiceDesk Plus ties agents and requesters to its own directory and authentication settings. In iTop, decide how agents authenticate, whether against your directory, a single sign-on broker or local accounts, and map profiles to roles before go-live. Confirm with Combodo or the iTop Hub which authentication modules your edition supports, because this varies by deployment. Remove dormant agent accounts as part of the access review.

Audit trail and change records

Auditors look for who changed a configuration item, when, and under which approved change. iTop records change management and CMDB history, but the retention period, log storage and export format depend on your configuration and how you forward logs. Confirm with your assessor which records they need, then test that a sample change can be traced from request to approval to the CMDB update. Exporting that trail is part of the migration plan.

Evidence for compliance assessments

DeployOpen can plan the controls, document how iTop is configured, and collect the evidence an assessor requests, such as access reviews, backup restores and change samples. It does not issue audit reports, attestations or certifications. Ask your auditor early which evidence format they accept and how long they want records kept, and write those requirements into the scope agreed before the work begins.

Running iTop with a small team or a larger installation

Combodo's published sizing suggests a single all-in-one iTop server for installations with fewer than 200 tickets a month and under 20 console users. The suggested baseline is 2 vCPU and 4 GB of memory, which covers the web application, PHP runtime and database on one machine. This layout is the simplest to build and back up, but it leaves no room for independent scaling or maintenance windows for each tier.

Baseline hardware: 2 vCPU and 4 GB of memory, per Combodo's requirements page.
Single point of failure: the web server, PHP and database share one host, so a failure takes the whole service down.
Backups: back up the database and the iTop configuration and extension files together, since they must match.
Growth trigger: plan a move to split servers once ticket volume or console users approach the suggested limits.
Test restores: rehearse a restore on a separate host before go-live, not after the first incident.

Confirm your actual ticket volume and concurrent console users with Combodo's sizing guidance before you commit to a single host.

What drives the cost of each option

The cost comparison turns on who is paid for what. On the ServiceDesk Plus side, the recurring line items are the license and maintenance tied to technicians and, for Professional and Enterprise editions, to assets, whether the product runs on-premises or in the cloud. Ask ManageEngine for the per-technician and per-asset rates that apply to your counts, the maintenance term, what the quote includes for upgrades, and whether CMDB and change management modules are priced separately from the base edition. On the iTop side, the software carries no license fee under the AGPL-3.0, but Combodo's agent-tiered offers (Community for up to 10 agents, Atelier for up to 50, Forge above 50) add support and tier costs if you choose a commercial plan. Confirm the current tier terms and whether you want on-premises or SaaS directly with Combodo.

The one-time costs on the iTop side are usually larger than the software decision suggests. Plan for server hardware or cloud instances sized to Combodo's guidance, database administration on MariaDB or MySQL, the PHP and GraphViz runtime, the migration of CMDB data, and extension work where your ServiceDesk Plus workflows, approvals or integrations do not map to standard iTop features. Each of these can be done by your team or by a partner, and the split is the main variable. Request a written breakdown that separates configuration, custom extension development, integration with your directory and monitoring tools, and training for administrators and agents, so you can compare it line by line with your current subscription.

Recurring costs on the iTop side are the infrastructure, patching and backups, the upgrades between releases such as 3.2.3-3 and 3.3.0, extension maintenance after each upgrade, and any Combodo support or retainer you buy. Costs rise with agent count, console users, ticket volume and the number of customized objects, and they fall when your CMDB data is clean and your workflows are standardized. Before you request quotes, count your technicians and assets, list every ServiceDesk Plus report, workflow and integration you rely on, and ask each vendor or partner to price the same list. Treat a quote that omits extension development or migration as incomplete.

How a move from ServiceDesk Plus to iTop runs at a high level

The sequence moves the CMDB, service definitions and request history into iTop in an order that keeps the data checkable at each stage, so cutover happens only after the new system has been validated against the old one.

Inventory the CMDB and classes
Your team lists the configuration items, relationships, request types, technician groups and approval paths that ServiceDesk Plus holds today, and marks which ones the business still uses. The owner of the CMDB and a service desk lead do this together, because they know which assets and services are actually referenced by change and incident work. The step is done when every data set you plan to move has a named owner and a decision to migrate, archive or retire it.
Map categories, SLAs and workflows to iTop objects
Each ServiceDesk Plus category, SLA, approval and workflow is matched to the iTop equivalent: the CMDB class model, customizable SLA definitions, the change management and approval configuration, and the ticket life cycle. Some ServiceDesk Plus logic will not have a one-to-one match, and those items go on a gap list with a decision on how to handle each. The step closes with a signed-off mapping document that the service desk and change managers have reviewed.
Export data from ServiceDesk Plus
Extraction uses query reports exported to CSV for most data sets. On on-premises installations, your database administrator may also read the underlying database directly, which gives more complete and consistent extracts for large histories. The export team keeps a record of each extract, including row counts and the date it was taken, so the same data can be reproduced later. The step is finished when every extract is stored in a controlled location and its row counts match the source.
Import data into iTop with CSV
The team loads the extracted CSV files into a staging instance of iTop using its CSV import, one class at a time, starting with the configuration items that other objects refer to. Records that fail import are logged and fixed at the source rather than edited by hand in iTop. The step is done when each class loads without unresolved errors and the record counts agree with the extracts. Historical tickets may be imported with the same process if the business wants them in iTop.
Run data consistency audits after import
Once data is loaded, iTop's data consistency audits check for records that break the model, such as orphaned relationships or missing mandatory fields. Your data owners review the findings, correct the source data, and re-import where needed until the audit output is acceptable to them. This step is also where you confirm that asset and service relationships needed for impact analysis are present. It closes when the audit results are documented and the remaining exceptions have an owner.
Rebuild automation and notifications
Notifications, triggers, escalation rules and integrations that ServiceDesk Plus performed are rebuilt in iTop, or delivered through extensions or custom work where iTop does not provide the same function out of the box. Your team confirms which features are covered by standard iTop, which need an extension from the iTop Hub, and which need integration work. The step is complete when each item on the gap list is either rebuilt, replaced or formally retired by its owner.
Run parallel validation
Service desk staff run realistic test requests through iTop while ServiceDesk Plus remains the system of record, and they compare routing, SLA clocks, approvals and change records against the expected results. Discrepancies are logged and traced back to the mapping, the import or the rebuilt automation. The step closes when the test cases have passed, the open defects are accepted by the process owners, and the business has agreed the cutover date.
Cut over and retain the source data
On the agreed date, the final delta data is exported from ServiceDesk Plus, imported into iTop, audited again, and iTop becomes the system of record for new requests. The ServiceDesk Plus instance is kept read-only for an agreed retention period so that historical questions can still be answered. The cutover is complete when the change log, the consistency audit results and the retention decision are all signed off by the service owner.

Questions buyers ask before choosing iTop over ServiceDesk Plus

How much effort does a move from ServiceDesk Plus to iTop take?

The effort depends mostly on how much of your ServiceDesk Plus configuration you need to rebuild in iTop, not on the data volume alone. Request history, the CMDB and asset records usually move through CSV import, while workflows, SLA definitions, notification rules and approval paths are typically rebuilt by hand in iTop's customizable model. Ask for a written inventory of your ServiceDesk Plus custom fields, workflows, SLAs and integrations before estimating, because those items drive the work.

Can our own team migrate to iTop without outside help?

A team with administration experience on a web application, a database and a change process can often do much of the work internally, especially for a single-site installation with a modest CMDB. Teams usually need help where the CMDB data model must match their real service and configuration relationships, where change management approvals must mirror existing controls, or where integrations with monitoring and identity tools must be built. Be honest with yourself about who will own iTop after cutover, because upgrades and extension management continue.

How long does an iTop migration take?

No duration figure is supplied for this migration, and the timeline depends on scope, the number of CMDB classes, custom workflows, integrations and how many users must be trained. Staging an environment, running a test import, reconciling data and planning a cutover window are separate phases, and each can take longer than the import itself. Ask any implementation partner for a written timeline tied to a fixed scope, and ask your own team to estimate the same phases against your ServiceDesk Plus inventory.

What skills does running iTop require?

Running iTop requires PHP and web server administration, a MySQL or MariaDB database that your team can back up and tune, and an understanding of ITIL-style change management so the configured approvals match your policy. iTop 3.3.x needs PHP 8.2 to 8.4 and MariaDB 10.6 to 11.8 is preferred, and it also needs GraphViz for diagrams. Developers who know PHP can build extensions, but a service desk administrator who understands your processes is equally important when designing classes and workflows.

Can we reproduce our ServiceDesk Plus reports in iTop?

Most standard ticket and asset reports can be reproduced in iTop, because its data model and its built-in query and export features cover common needs, including impact analysis views. Custom reports built on ServiceDesk Plus-specific tables or report designers will need to be recreated, and some may need extensions. Export your current reports first, then test each one against imported data to confirm that counts, date ranges and SLA calculations match before you retire the old system.

How does iTop licensing change with the number of agents?

Combodo offers iTop Community free for up to 10 agents, iTop Atelier for up to 50 agents and iTop Forge for more than 50 agents, each available on premises or as SaaS. Because the software itself is AGPL-3.0 licensed, the recurring costs shift toward infrastructure, operations and any Combodo support, training or consultancy you buy. Confirm the agent count definition and the tier that matches your largest realistic growth scenario with Combodo before you sign.

When should we hire an implementation partner for iTop?

Consider a partner when your CMDB model is complex, when you need a hardened production deployment with backups and upgrades planned, or when your team cannot commit the time to run a parallel cutover. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure, typically under a fixed scope agreed in writing before work starts. Ask for the written scope, deliverables and support terms before comparing quotes, since DeployOpen does not publish a price list.

How DeployOpen scopes an iTop evaluation or migration

DeployOpen starts every iTop engagement with a written scope and a deliverables list agreed before any work begins. For a ServiceDesk Plus Enterprise customer, that scope usually separates three tracks: an evaluation that tests iTop against your current CMDB and change process, a migration that moves data and rebuilds workflows, and a production hardening phase. The scope document should name the ServiceDesk Plus modules in use, the number of technicians and end users who will work in iTop, whether iTop runs on premises or as SaaS, and which records are in scope for migration. Ask for the scope in writing and check that each deliverable can be tested by someone on your side, such as a mapped CI class model, a list of rebuilt change approval paths or a reconciled ticket count from the export.

The most time-consuming part is usually CMDB and workflow mapping. iTop's data model is customizable, so the team has to decide which configuration items, relationships and lifecycle states match the ones you keep in ServiceDesk Plus, and which ones should be dropped. Change management, SLA rules and notification templates also need to be rebuilt by hand, since they do not transfer as configuration. Extension selection comes next: iTop's functional coverage depends on extensions distributed through the iTop Hub, and each one must be checked for licensing, version compatibility and maintenance status before it is put into your scope. Integration work for directory sources, monitoring feeds or discovery tools is priced and planned separately. DeployOpen does not act as a Combodo partner or reseller unless a written agreement says otherwise, so confirm with Combodo which support and training options apply to your edition and agent tier.

Hardening, backups and upgrades are defined in the scope, not left for after go-live. The deliverables should cover the web and database tiers, the MariaDB or MySQL backup routine, restore testing, PHP and GraphViz versions, and a plan for applying iTop point releases. Once the system is live, ongoing support, upgrades and testing can run under a retainer, which is a recurring agreement separate from the fixed-scope project. Ask for the retainer terms, response expectations and what is excluded before you sign. Ask DeployOpen to show how each control will be evidenced for your audit or assessment, while remembering that DeployOpen prepares that evidence and independent auditors issue any assessment result.

How DeployOpen helps evaluate, implement and migrate iTop

DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure. For ServiceDesk Plus Enterprise customers moving their CMDB and change management to iTop, we start with the written scope and work through your configuration items, processes and integrations before anything is built.

How we scope

We map your current CMDB classes, change workflows and SLA rules against iTop's customizable data model before agreeing scope.
Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
Scope should list which extensions, integrations and data migrations are in or out, so the quote follows from defined work.

How we build

We install iTop on your chosen servers, sized against the PHP, MariaDB and GraphViz requirements Combodo publishes for your ticket and console user volumes.
We configure the CMDB, change management, impact analysis and SLA definitions, then test them against your real request types.
Where ServiceDesk Plus workflows need extensions or custom integration, we build, test and document that work as a separate deliverable.

How we hand over

You receive configuration documentation, data mapping records, test results and runbooks for administrators and agents.
We run a cutover rehearsal with your administrators so the change and incident process is confirmed before go-live.
Backup, restore and upgrade procedures are written for your environment, so your team can operate iTop without DeployOpen on site.

How we support

Ongoing support, upgrades and continuous testing are available as retainers after handover.
Security testing of the iTop application and its integrations can be scoped separately, with findings and remediation tracked to closure.
Before any upgrade, we confirm the target iTop release and its requirements with you, then test the change in a non-production copy.

ManageEngine ServiceDesk Plus vs iTop