When ServiceNow or iTop fits your ITSM estate
ServiceNow fits when its platform breadth is already in use, so the choice is less about the service desk and more about what sits around it. A renewal, a data residency requirement or a CMDB that has outgrown its tooling usually starts the review, but the decision turns on whether your team relies on ServiceNow's workflows, integrations and vendor-run cloud, or mainly on incident, change and asset records. If most of your estate depends on those integrations, moving to a self-hosted tool means rebuilding them, and the cost of that rebuild belongs in the comparison from the start. Treat that as the first test. List the modules you actually operate, the integrations that feed or read from them, and the number of agents who work in the tool each day. Ask ServiceNow for its current pricing and deployment options in writing, and confirm with your account team what a Private Stack deployment would require before you compare it with self-hosting.
iTop fits when the CMDB and impact analysis are the core of the work and your organization wants to run the service desk on its own servers. Its graphical impact analysis, customizable CMDB, change management, SLA and contract management, and data synchronization for federation cover much of the ITSM work that depends on configuration data. The skills are the other half of the decision: iTop runs on PHP with MySQL or MariaDB, so your team needs to operate that stack, and the requirements page lists PHP 8.2 to 8.4, MariaDB 10.6 to 11.8 and GraphViz. Check three things before you commit. Count your agents against the Community edition limit of 10 and the Atelier and Forge tiers, confirm which integrations you need, and assess whether your staff can own upgrades, backups and the database. Note that ServiceNow's ecosystem is broader, so verify iTop's coverage against your actual workflows rather than assuming it.
Which option fits each scenario
This table maps common ServiceNow ITSM situations to whether iTop, ServiceNow cloud or ServiceNow Private Stack fits best, and the condition under which each fit holds. Read each row against your own agent count, data rules and team skills, because the answer usually changes when one condition changes.
| Scenario | Better fit | Why and when it holds |
|---|---|---|
| CMDB-centered service management | iTop | iTop's customizable CMDB, graphical impact analysis and data synchronization suit teams whose ServiceNow use centers on configuration items and relationships, provided they can model their CI classes in iTop. |
| Broad ITSM with many workflows and integrations | ServiceNow cloud | Holds when you depend on many custom workflows, a wide platform app catalog and deep integrations. Confirm each required integration exists in iTop or in its extension hub before choosing iTop. |
| Data must stay in the organization's own data center | iTop | Self-hosting iTop inside your own facilities keeps records on your servers. ServiceNow Private Stack also keeps data on premises, but you would then operate its load balancer, application and database tiers yourself. |
| Under 10 agents | iTop Community | Combodo offers iTop Community free for up to 10 agents. Confirm current edition terms with Combodo, and count agents, not all console users, when you test the fit. |
| More than 50 agents | iTop Forge | Combodo's Forge edition covers more than 50 agents. Ask Combodo for the commercial terms and support scope for your agent count before budgeting the move. |
| Air-gapped networks | iTop or GLPI, self-hosted | Holds when no internet path exists. ServiceNow Private Stack can run offline but still needs ServiceNow upgrade packages and support, so compare operating effort in the air-gapped comparison page. |
| Small team without PHP or database operations skills | ServiceNow cloud or a managed partner | Running iTop needs PHP 8.2 to 8.4, MariaDB, GraphViz and patching. If nobody on staff can own those tiers, a managed hosting arrangement or a partner should run it. |
| Planned move from Private Stack to self-hosting | iTop, with a sized pilot | Private Stack already requires you to run the web, application and database tiers, so the skills gap is smaller. Test iTop on a copy of your CMDB data and confirm the ServiceNow export path before committing. |
How far iTop's CMDB and data synchronization replace ServiceNow's CMDB
iTop's CMDB is fully customizable, so you can model your own CI classes and the relationships between them, and those relationships drive graphical impact analysis when a change or outage is planned. Data synchronization supports federation, which lets iTop feed or be fed by other instances rather than forcing one database to hold everything. Before you rely on that, count the CI classes and relationships your ServiceNow CMDB actually uses today, not the ones the schema offers. Many estates use a small core of server, application, service and business service classes with a handful of dependency links, and that subset is far easier to rebuild than a full export suggests. Also check whether any of those CIs are populated by ServiceNow Discovery or by integrations with monitoring, cloud or endpoint tools. Each source is a feed you must replace, and iTop's CSV import and data consistency audits cover loading and checking records, not discovering them on the network.
Decide now how the CMDB will be fed once Discovery is removed. Options include inventory from the GLPI Agent if you run GLPI alongside iTop, scheduled CSV loads from existing scripts, or API-based synchronization from your monitoring and cloud platforms. Each option has a different owner and a different failure mode, so write down who maintains each feed and how stale data will be detected. Ask Combodo, or check the iTop documentation, which synchronization connectors are supplied and which need custom work, because that determines the effort in your quote.
Run a proof of concept on a copy of real data, not a sample. Import a representative set of CIs and relationships through CSV, run the consistency audits, then trace an impact analysis for a known change and compare the result with what your change advisory board expects. Record every record that fails to import or audit and every relationship that does not appear in the graph. Those results, not the feature list, tell you whether iTop replaces the parts of ServiceNow's CMDB your teams depend on.
Choosing between the Community, Atelier and Forge editions
Combodo offers iTop Community free for up to 10 agents, available either on premises or as SaaS. It is the edition most small IT teams start with, and it carries the full CMDB, helpdesk, change, SLA and contract functions described for iTop. The practical limit is headcount: an agent is a person working tickets in the service desk, so a team that grows past ten agents has to plan for a different edition rather than discover the limit after rollout.
- Team size: Ten agents covers a small internal IT group, but count everyone who will work tickets, including on-call staff and shared service desk roles.
- Deployment choice: The same agent cap applies whether you run it on premises or use the SaaS option, so the deployment decision does not change the licensing band.
- Feature scope: Community includes the CMDB, change, SLA and contract management, so small teams do not lose core ITSM functions.
- Growth planning: Model headcount for the next budget cycle, because moving up a band later means a licensing change and possibly a re-check of your deployment.
- Extensions: Confirm which extensions from the iTop Hub are supported on Community before you depend on them.
Confirm the current Community agent limit and terms with Combodo before deciding, since editions can change.
iTop Atelier is the edition for teams of up to 50 agents, offered on premises or as SaaS. It sits between the free Community tier and Forge, and it fits organizations that have outgrown the ten-agent cap but do not need the larger band. The gap between Community and Atelier is mainly a licensing decision, so compare the commercial terms against your real agent count and growth expectations.
- Team size: Atelier covers mid-sized service desks where many people touch tickets, including IT operations, field support and change approvers who act within the tool.
- Commercial support: Combodo sells commercial support, training and consultancy for iTop, so ask which of these are included in each band.
- Deployment: Choose on premises or SaaS based on your data residency and hosting rules, which the agent band does not decide.
- Extensions: Check that the extensions you plan to use are available through the iTop Hub and are compatible with your edition.
- Recurring costs: Confirm with Combodo whether licensing and support renew annually and what changes at renewal.
Confirm current Atelier pricing, inclusions and agent definitions with Combodo before you commit.
iTop Forge is the edition for more than 50 agents, again available on premises or as SaaS. It suits larger service desks where many teams share one CMDB and where support and training needs grow with the number of users. Because the band is open-ended, the commercial conversation should start with a precise count of agents and a plan for how they will be organized.
- Team size: Forge applies to organizations with more than 50 agents across several service desks, which makes agent counting and role design part of the scope.
- Shared CMDB: Larger estates often rely on data synchronization and consistent CI classes across teams, so plan governance early.
- Consultancy and training: Combodo sells consultancy and training, which becomes more relevant as the number of administrators and process owners grows.
- Infrastructure sizing: Combodo's requirements page describes separate web and database servers for larger installations, so budget infrastructure alongside licensing.
- Renewal terms: Ask how the agent count is measured and how additional agents are added during the term.
Confirm the Forge terms, agent definitions and support levels with Combodo before deciding.
ServiceNow sells ITSM as a subscription that you quote through its account team, so there is no public price to compare directly with iTop's editions. Its cost is driven by the modules, user types and platform components in your contract, not by a single agent band. Comparing the two fairly means putting the ServiceNow quote and the iTop edition terms side by side, with every component listed.
- What you are paying for: Ask the account team to itemize modules, user and fulfiller counts, environments and included support.
- Platform breadth: ServiceNow includes platform capabilities that an iTop estate may not need, so decide which of them your processes actually use.
- Recurring versus one-time: Separate annual subscription fees from implementation, integration and training costs.
- Operating costs: Add the administrators and infrastructure you carry for iTop, since the software license is only one part of total cost.
- Exit terms: Ask what data export and contract termination look like before you compare long-term totals.
Confirm the ServiceNow quote in writing and confirm iTop's current edition terms with Combodo before you decide.
Where your ITSM data lives under each option
Under ServiceNow cloud, ServiceNow operates the platform, the database and the hosting tiers, so your incident, change and CMDB records sit in infrastructure you do not run. ServiceNow Private Stack changes that boundary. The customer or a partner owns and operates the load balancer, application server and database tiers, while ServiceNow supplies the application software, upgrade packages and support. Before choosing it, confirm with your ServiceNow account team which tiers your own staff will patch, back up and monitor, and what the workshop ServiceNow expects for Private Stack covers in architecture, hardware sizing and database selection, since those decisions set where your data physically resides.
With iTop, the same question has two answers. Self-hosted iTop runs in your own data center or cloud accounts, with the web server, PHP runtime and MariaDB or MySQL database under your control, so the CMDB, ticket history and attachments stay where you put them. Combodo also offers iTop as SaaS, which moves hosting and database operations to the vendor. Ask Combodo in writing where the SaaS instance is hosted, who holds administrative access to the database, how backups are encrypted and where they are kept, and how a data export works at exit. The answers determine whether your records remain inside your own accountability boundary.
Whichever option you pick, identity, audit and compliance controls are things your organization must design, operate and evidence. Decide how administrator and agent accounts authenticate, which roles can edit CMDB classes and change approvals, and how audit logs of those edits are retained and reviewed. DeployOpen can help plan these controls, configure them and prepare the evidence an assessor will ask for, but independent auditors and certification bodies issue any reports or attestations. Document the design now, because a gap in access logging or backup coverage is much harder to explain during an assessment than a missing feature.
What drives the cost of each option
This table sets the ServiceNow cloud, ServiceNow Private Stack and self-hosted iTop cost components side by side, with who is paid, whether each cost is one-time or recurring, and what moves it. Use it to build a like-for-like quote request, since no iTop or ServiceNow prices are stated here.
| Cost component | Who is paid and for what | One-time or recurring, and what drives it |
|---|---|---|
| ServiceNow subscription (cloud) | ServiceNow, through the account team, for the platform subscription | Recurring. Driven by the subscription scope, user and module counts, and renewal terms. Ask for the full scope in writing. |
| ServiceNow Private Stack workshop | ServiceNow, for architecture planning, hardware sizing, database selection and operational readiness | One-time. Customers starting a deployment should expect to buy it, so ask whether it is priced separately from the subscription. |
| Private Stack infrastructure | Your data center or cloud provider, plus staff who run the load balancer, application and database tiers | Mostly recurring. Driven by hardware sizing from the workshop, operations headcount and upgrade effort. |
| iTop Community or paid editions | Combodo, for the Community, Atelier or Forge license tier, on premises or as SaaS | Community covers up to 10 agents free. Atelier (up to 50 agents) and Forge (more than 50 agents) are recurring. Agent count is the main driver. |
| iTop hosting and database operations | Your infrastructure team or hosting provider for servers, PHP 8.2 to 8.4, MariaDB 10.6 to 11.8 and GraphViz | Recurring. Combodo suggests one all-in-one server for fewer than 200 tickets a month and under 20 console users, and separate web and database servers above that. Ask your team to size against those figures. |
| iTop implementation and customization | DeployOpen or another integrator, for the CMDB model, SLAs, change workflows and CSV or data synchronization | One-time, with later change requests. Driven by the number of CI classes, workflows and integrations you rebuild. |
| Commercial support and training (optional) | Combodo, for support, training and consultancy | Recurring if bought. Confirm the support tier, response scope and whether it covers upgrades. |
| Backups, upgrades and staff time | Your IT operations team or a retainer partner, for backups, upgrade testing and on-call support | Recurring. Driven by upgrade frequency, testing depth and the number of people who know the stack. Ask for a documented runbook as part of the quote. |
What a move from ServiceNow to iTop involves
The sequence turns ServiceNow incidents, assets and configuration items into a CMDB-centered iTop service desk that runs in your own infrastructure, with each stage closed by a check the team can verify before the next one starts.
Inventory modules, CI classes and integrations
Your team lists the ServiceNow modules in use, such as incident, problem, change, service catalog, SLA and CMDB, along with the CI classes, relationships, approval rules and every integration that writes to or reads from ServiceNow. DeployOpen can run this inventory as part of a fixed-scope plan if you want an outside review. It is done when each module and integration has an owner and a named iTop equivalent or a decision to drop it.
Export ServiceNow data within its limits
Export records in the formats and volumes ServiceNow allows, then extract attachments separately, since list exports do not carry them. Confirm which record limits apply to your instance and which exports need a MID Server or an administrator to enable them. The step is complete when row counts for each table match the source and the exported files are stored in an access-controlled location.
Stand up the iTop environment on the chosen sizing
Install iTop on PHP 8.2 to 8.4 with MariaDB 10.6 to 11.8 (MariaDB is preferred over MySQL 8 for performance), plus GraphViz for impact diagrams. Combodo suggests an all-in-one server with 2 vCPU and 4 GB of memory for fewer than 200 tickets a month and under 20 console users, and separate web and database servers of up to 8 vCPU and 16 GB for larger installations. Your team or a partner handles hardware, backups and hardening. It is done when a test instance runs under the expected load profile and backups restore cleanly.
Map CI classes and relationships to the iTop CMDB
Translate ServiceNow tables and CI classes into iTop classes and relationships, then decide which fields, lifecycle states and attributes you need to customize. iTop's CMDB is fully customizable, so this design work is where most of the effort sits. Record the mapping in a signed-off document. It is done when every exported table has a target class, every relationship type is defined, and reviewers have approved the data model.
Load data through CSV import
Transform the exports into the CSV layout iTop's import expects, load reference data such as organizations, persons and teams first, then CIs and tickets. Load in small batches on the test instance and log rejected rows. It is done when the imported counts reconcile with the source exports and the rejected rows are either fixed or documented as intentionally dropped.
Rebuild SLAs, change workflows and impact analysis
Recreate service level agreements, contract links, change approval paths and notification rules in iTop, then test graphical impact analysis against known CI relationships. Workflows and catalog items usually have to be rebuilt by hand rather than carried over. It is done when test scenarios for incidents, changes and SLA breaches produce the outcomes your process owners expect, and impact diagrams show the dependencies they know about.
Run data consistency audits and reconcile integrations
Run iTop's data consistency audits to find orphaned records, missing relationships and invalid values, then fix them at source. Rewire each integration that used to call ServiceNow, including monitoring, identity and discovery feeds, and confirm which systems now write to iTop through its API or data synchronization. It is done when audits return no open findings for critical classes and each integration has a tested owner and failure path.
Parallel run, cut over and retire ServiceNow
Run iTop alongside ServiceNow for a agreed period so teams can compare tickets, changes and CMDB views, then freeze ServiceNow for writes and perform a final delta load. After cut over, keep read-only ServiceNow access and exports for the retention period your policies require before decommissioning. Confirm the retention window with your compliance owner. It is done when stakeholders sign off the parallel results and the retirement record lists where archived data is stored.
Questions buyers ask before moving from ServiceNow to iTop
What does a switch from ServiceNow to iTop cost?
The cost is mostly people and services, not software, because iTop's license is free under AGPL-3.0 and the Community edition costs nothing to download. Your budget will cover the infrastructure to host iTop, the work to map and load your ServiceNow records, rebuilding SLAs and change workflows, testing, training, and any paid support or edition you choose. Costs rise with the number of CI classes, the volume of history you keep, the number of integrations to rebuild, and the number of agents. Ask Combodo to confirm current edition terms and what its commercial support covers, and ask any implementation partner for a fixed-scope quote built from your written requirements. Your ServiceNow renewal terms and any exit fees will also shape the total.
How long does a ServiceNow to iTop migration take?
The timeline depends on how much of your ServiceNow estate you actually need to move, so there is no reliable duration without a scoped assessment. The main drivers are the size and quality of your CMDB data, how many custom workflows, catalog items and integrations must be rebuilt, the number of approval and SLA rules, and how many rounds of user acceptance testing your change board requires. Parallel running with ServiceNow for a period of reporting and audit access also extends the schedule. Ask for a written timeline with milestones tied to each deliverable, and treat any duration given without a scope as an estimate to challenge.
What does the internal team need to provide during the move?
Your team supplies the knowledge that no export contains. Process owners need to confirm how incidents, problems, changes and service requests really flow today, including which steps are informal. A CMDB owner must decide which CI classes, relationships and attributes matter, and data owners must agree what to cleanse before loading. Security and compliance staff should define access roles, audit evidence and retention rules. Expect ongoing time from the service desk lead for testing and training, and from the infrastructure team for hosting decisions. Name these people before work starts, because delays in decisions are often the largest timeline risk.
Can our own IT team migrate ServiceNow to iTop without a partner?
A capable team with PHP, database and ITSM experience can run the platform and do parts of the migration, but the work is more than a data copy. Load of CI records through iTop's CSV import is manageable for a team that understands data consistency, while rebuilding SLAs, change workflows and impact analysis requires configuration knowledge that is easy to underestimate. Consider whether your staff have time alongside daily operations, and whether they can own the system after go-live. Many organizations split the work: internal staff own data and process decisions, and an outside specialist handles the technical build, hardening and documentation. Choose the split based on a written skills assessment rather than assumptions.
Does iTop replace every ServiceNow workflow and integration?
No single open-source tool replicates the full ServiceNow platform, so the honest answer is that iTop covers ITSM and CMDB core processes while some workflows and integrations need rebuilding or a different tool. iTop's documented scope includes a customizable CMDB, helpdesk and incident management, service and contract management, change management, customizable SLA management, graphical impact analysis, CSV import, data consistency audits and data synchronization for federation. Anything outside that, such as custom application development on the ServiceNow platform, some ServiceNow integrations or specialized operational modules, must be listed and assessed one by one. Map every ServiceNow integration you depend on, then confirm with Combodo whether iTop supports it natively, through an extension from the iTop Hub, or through custom work.
What happens to the 10-agent limit on iTop Community as the team grows?
The Community edition is free for up to 10 agents, and the limit is the trigger for choosing a paid edition. Combodo offers iTop Atelier for up to 50 agents and iTop Forge for more than 50 agents, each available on premises or as SaaS. Growth decisions should be made on a written count of agents who actually use the service desk, because pricing depends on that number and on the edition chosen. Ask Combodo to confirm how agents are counted, whether read-only or requester users count, and what changes when you move between editions. Plan the budget for the step-up before go-live, not after the team exceeds the limit.
How do we run the PHP and MariaDB stack that iTop needs?
iTop 3.3.x requires PHP 8.2 to 8.4, supports MySQL 5.7 or later and MariaDB 10.6 to 11.8, and needs GraphViz for diagrams. MariaDB is the preferred database, and MySQL 8 is discouraged for performance reasons. Combodo suggests an all-in-one server with 2 vCPU and 4 GB of memory for fewer than 200 tickets a month and under 20 console users. Larger installations use separate web and database servers, with sizing up to 8 vCPU and 16 GB each. Your operations team needs routine PHP and database patching, backups tested by restore, TLS configuration, and monitoring of the GraphViz dependency. Confirm the current version matrix on the requirements page before you build, because supported versions change between releases.
How DeployOpen helps evaluate and implement iTop
DeployOpen is a Chainscore Labs company that plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted iTop inside your own infrastructure, whether that is your cloud accounts, data center or air-gapped network. For a ServiceNow team, the useful first step is an evaluation scoped to your actual records: which CI classes must exist in the CMDB, which SLAs and contracts drive escalations, and which change approvals need to survive the move. Those answers decide the data model, the agent count and the hosting layout before any installation starts. DeployOpen can also run security testing on the finished application and its APIs and prepare the systems, controls and evidence your compliance assessment will ask for. DeployOpen does not issue audit reports or certifications; independent auditors and certification bodies do that work.
Most engagements are fixed-scope. Before work starts, the scope, deliverables and timelines are agreed in writing, and the quote follows from that written scope rather than from a published price list, which DeployOpen does not maintain. Ask for the written scope to name the PHP 8.2 to 8.4 runtime, the MariaDB version, the GraphViz dependency, the web and database server sizing, and who owns the Combodo support relationship. Ongoing upgrades, continuous testing and support are available as retainers, which matters because iTop releases such as 3.3.0 and 3.2.3-3 will need to be applied in your environment. DeployOpen is not an official Combodo partner unless a partnership is confirmed in writing, so confirm that status directly with Combodo before you rely on it for licensing or commercial support.
