Migrate your iTop data
Open-source ITSM and CMDB platform built for IT operations teams, with a free Community edition and paid subscription tiers for enterprise support and extensions.
In its favor
Why people choose iTop
The signal that keeps iTop on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Free Community edition provides full ITSM and CMDB capabilities without licensing costs, making it popular among small IT teams and cost-sensitive organizations.
Highly customizable data model and class definitions allow organizations to adapt the platform to their specific IT service processes.
Open-source model with an active community provides extensions and third-party integrations through the iTop Hub store.
Built-in CMDB capability with CI classes for servers, applications, network devices, and business services without additional modules.
Incident and change management workflows are included out of the box with configurable approval processes and status tracking.
Outdated user interface with legacy table-based layouts feels dated compared to modern ITSM platforms with cleaner UX and better mobile support.
Complex initial setup and steep learning curve for administrators unfamiliar with PHP-based applications and XML configuration.
Limited out-of-the-box reporting and analytics compared to enterprise platforms like ServiceNow or Jira Service Management.
Performance issues reported with large datasets and complex CMDB relationships in Community edition.
Customer support quality is inconsistent, with lower ratings in the Community edition compared to paid subscription tiers.
Reasons to switch
Why people leave iTop
The recurring reasons buyers give for replacing iTop. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where iTop fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
iTop pricing overview
iTop offers a free Community edition for on-premise deployments, with paid Professional and Enterprise subscription tiers available directly from Combodo. Subscription pricing is per-organization rather than per-user and includes expert support, additional extensions, and the graphical Designer tool in paid tiers. SaaS hosting is available on Professional and Enterprise plans.
Community
Tier 1 of 3
Free (open source)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on iTop's schedule — see our quote-based pricing →
What gets migrated
iTop object support
Object-by-object support for iTop migrations. Per-pair details surface during scoping.
Tickets (User Requests)
Fully supportedUserRequest is the primary ticket object in iTop. We export all standard fields including title, description, functional_ci, services, priority, status, and assignee. The OQL export includes all linked changes and incidents via foreign key resolution.
Incidents
Fully supportedIncident class inherits from Ticket and includes caller, impacted_ci, and责任的 assignment fields. We preserve the incident timeline and linked knowledge base articles during migration.
Change Requests
Fully supportedChangeRequest objects include type (normal, urgent, emergency), approval statistics, and rollback plan fields. We map these to the destination's change management object with status translation.
Services and Service Subcategories
Mapping requiredServices are linked to SLA definitions and provider contracts. We export service hierarchies but require value-mapping on the destination since service catalog structures differ between platforms.
Configuration Items (CIs)
Mapping requirediTop's CMDB supports multiple CI classes including Servers, Network Devices, Applications, and Databases. We export CI relationships but the class naming and attribute schema require field-level review before import.
Contacts
Fully supportedContacts include person details, email, phone, and organization membership. We map these to the destination's contact or person object with organization linking preserved.
Organizations
Fully supportedOrganizations are top-level entities that group Contacts and CIs. We export organizations with their hierarchical structure intact.
Users and Roles
Mapping requiredUser accounts include login, password hashes, and profile assignments. Direct migration of user credentials is not supported; we export account metadata and role mappings for manual recreation on the destination platform.
Custom Objects
Mapping requirediTop allows defining custom classes via XML extensions. We export custom object data but each custom class schema must be reviewed and mapped individually to the destination's equivalent.
Attachments
Mapping requiredAttachments are stored as files linked to tickets and CIs. We export attachment metadata and file paths. File storage format differs between source and destination, requiring file re-upload during migration.
Knowledge Base Articles
Mapping requiredFAQ and KB articles have title, content, and category fields. We export article content in structured format for re-import, but category structures require manual mapping.
SLA Definitions
Mapping requiredSLA definitions include escalation matrices and response/resolution time targets. We export SLA configurations but escalation rules are platform-specific and require reimplementation.
| Object | Support | Notes |
|---|---|---|
| Tickets (User Requests) | Fully supported | UserRequest is the primary ticket object in iTop. We export all standard fields including title, description, functional_ci, services, priority, status, and assignee. The OQL export includes all linked changes and incidents via foreign key resolution. |
| Incidents | Fully supported | Incident class inherits from Ticket and includes caller, impacted_ci, and责任的 assignment fields. We preserve the incident timeline and linked knowledge base articles during migration. |
| Change Requests | Fully supported | ChangeRequest objects include type (normal, urgent, emergency), approval statistics, and rollback plan fields. We map these to the destination's change management object with status translation. |
| Services and Service Subcategories | Mapping required | Services are linked to SLA definitions and provider contracts. We export service hierarchies but require value-mapping on the destination since service catalog structures differ between platforms. |
| Configuration Items (CIs) | Mapping required | iTop's CMDB supports multiple CI classes including Servers, Network Devices, Applications, and Databases. We export CI relationships but the class naming and attribute schema require field-level review before import. |
| Contacts | Fully supported | Contacts include person details, email, phone, and organization membership. We map these to the destination's contact or person object with organization linking preserved. |
| Organizations | Fully supported | Organizations are top-level entities that group Contacts and CIs. We export organizations with their hierarchical structure intact. |
| Users and Roles | Mapping required | User accounts include login, password hashes, and profile assignments. Direct migration of user credentials is not supported; we export account metadata and role mappings for manual recreation on the destination platform. |
| Custom Objects | Mapping required | iTop allows defining custom classes via XML extensions. We export custom object data but each custom class schema must be reviewed and mapped individually to the destination's equivalent. |
| Attachments | Mapping required | Attachments are stored as files linked to tickets and CIs. We export attachment metadata and file paths. File storage format differs between source and destination, requiring file re-upload during migration. |
| Knowledge Base Articles | Mapping required | FAQ and KB articles have title, content, and category fields. We export article content in structured format for re-import, but category structures require manual mapping. |
| SLA Definitions | Mapping required | SLA definitions include escalation matrices and response/resolution time targets. We export SLA configurations but escalation rules are platform-specific and require reimplementation. |
Gotchas
What to watch for in iTop migrations
Issues we've hit on past iTop migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Beta version 3.2.0 known issues affect data integrity
No direct workflow migration between platforms
API rate limits and edition gating undocumented
Custom class schema variations require manual mapping
Attachment storage format not portable
| Severity | Issue |
|---|---|
| High | Beta version 3.2.0 known issues affect data integrity |
| High | No direct workflow migration between platforms |
| Medium | API rate limits and edition gating undocumented |
| Medium | Custom class schema variations require manual mapping |
| Medium | Attachment storage format not portable |
Leaving iTop?
Where iTop customers move next
7 destinations iTop can migrate to.
How a iTop migration works
Four steps, iTop-specific
Connect
Session-based authentication (cookies) into iTop. Scopes limited to read-only on the data we move.
Map
We translate iTop-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate iTop quirks before production.
Migrate
Full migration with iTop rate-limit handling. Rollback available throughout.
FAQ
iTop migration FAQ
Answers to the questions buyers ask most during iTop migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your iTop migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate iTop.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your iTop setup and destination — written quote back within a business day.