When a self-hosted Freshservice alternative makes sense with iTop
A self-hosted iTop deployment makes sense when a renewal, a per-agent or asset unit cost question, or a need for a configurable CMDB on your own servers has forced the question of who will run the service desk. Freshservice fits teams that want a managed service with little to operate: the vendor hosts the application, applies upgrades and carries the platform. iTop fits teams that will own hosting, database maintenance, upgrades, backups and the data model themselves. Neither choice is wrong, but they are different operating commitments, and the reader should decide which one their team can carry before comparing feature lists.
The first decision point is CMDB complexity. iTop is built around a customizable CMDB, with graphical impact analysis, data consistency audits and data synchronization for federation, so it rewards organizations that have a defined model of applications, services, contracts and configuration items they want to maintain. If your asset needs are closer to a flat inventory with check-out and renewal dates, the extra modeling effort may not return much. Second, count your agents. iTop Community is free for up to 10 agents, and Combodo's paid editions, iTop Atelier and iTop Forge, cover larger groups on premises or as SaaS. Confirm current tier terms and what each edition includes directly with Combodo before you size the project, because the boundary between free and paid use decides the cost structure. Third, assess in-house operating capacity. Someone must maintain PHP 8.2 to 8.4 and MariaDB or MySQL, GraphViz, backups and upgrades. Combodo's iTop software requirements page is the place to check current versions against your standards.
Which option fits which IT operating model
This table matches common Freshservice-replacement situations to the platform that usually fits best, and names the condition that drives the choice. Read each row against your own agent count, data rules and in-house skills, then check the paid edition or managed hosting column before assuming the answer holds.
| Operating model | Better fit | Driving condition and what changes the answer |
|---|---|---|
| Small team with under 10 agents | iTop Community | The free Community edition covers up to 10 agents. Confirm the agent definition with Combodo, because a larger console group moves you to a paid edition. |
| Many relationships between services, assets and contracts | iTop | iTop's configurable data model and graphical impact analysis suit teams that need to trace what a change affects. Freshservice's asset units and GLPI's asset records can also model relationships, so test your own impact questions on both. |
| Strict EU or on-premises data rule | iTop on your own servers | Self-hosting keeps tickets and CMDB data inside your infrastructure. Freshservice's Frankfurt data center is regional hosting, so it does not remove vendor access questions. Check the wording of your rule with your compliance lead. |
| No database or PHP operators in house | Freshservice or a managed iTop deployment | iTop needs PHP 8.2 to 8.4, MySQL or MariaDB and GraphViz. Without people who can run that stack, budget for a partner or choose a vendor-run service. Combodo's SaaS option, if chosen, moves operation to the vendor. |
| Wants a vendor-run SaaS service desk | Freshservice or iTop SaaS | Freshservice runs the application for you. iTop is also offered as SaaS by Combodo, so compare the terms, data location and exit options of each before deciding. |
| Mid-sized team needing change and SLA management in one tool | iTop | iTop's README lists change management and customizable SLA management in the base product. Confirm that your approval paths and SLA rules can be expressed in its data model before migrating. |
| Team that also needs broad asset discovery and financial records | GLPI with GLPI Agent | GLPI includes native inventory through its agent and contract management. iTop covers CMDB work well, but discovery and financial tracking may need extensions from the iTop Hub. Confirm coverage in a proof of concept. |
| Team that wants a large paid tier for more than 50 agents | iTop Forge or GLPI, by quote | Combodo's paid editions scale by agent count and run on premises or as SaaS. Ask for written pricing for your agent count, and compare it with GLPI's free license plus your own hosting and support costs. |
How iTop's configurable CMDB changes the asset model
iTop starts from a configurable CMDB, not from an asset list. Configuration items, the relationships between them and the lifecycle rules attached to each class are the core of the product. The README describes graphical impact analysis, customizable SLA management, change management and data consistency audits on that same model. Freshservice meters its asset management through asset units, with a set number included per plan and more sold in packs, and it tracks assets as inventory records tied to tickets and workflows. The practical difference is where the model lives: in iTop, the data model is something your team shapes and maintains, and the impact of an outage or change is read from the links between items rather than from the ticket alone.
The CMDB depth matters when you need to answer questions such as which business services depend on a database server, what a planned change to a network device touches, or which approvals a change needs before it runs. It also matters when several instances must exchange data, since iTop offers data synchronization for federation. If your asset needs are mostly hardware and software records, check-out and renewal dates, and tickets raised against them, a simpler register is usually enough, and a heavier CMDB adds modeling and upkeep work without a matching return.
Before you choose, list the relationship types your change and incident processes depend on, such as "runs on", "depends on" or "is owned by", and the lifecycle states each class must pass through, such as ordered, in service, retired. Confirm with your change manager who approves what and which fields must be populated before an item can move on. Ask Combodo or an implementation partner to walk through those rules against iTop's documentation, because the effort to rebuild them in a new data model is usually where a migration takes longest.
Which capabilities iTop covers against Freshservice
This table compares the ITSM, CMDB and licensing capabilities that matter when moving from Freshservice to iTop. Where a Freshservice detail is not in our research, the cell tells you what to confirm in your own plan and tenant. Read the gaps column first, since they shape the migration scope more than the matched features.
| Capability | iTop (Combodo) | Freshservice: what to confirm |
|---|---|---|
| Helpdesk and incident management | Helpdesk and incident management are part of the core iTop README feature set | Confirm ticket types, queues and agent roles in your plan and tenant |
| Change management | Change management is listed in the iTop README; workflows must be modeled in iTop's data model | Confirm which change approval flows and CAB steps your tenant uses today |
| SLA management | Customizable SLA management is listed in the iTop README; targets are configured in iTop | Export your SLA definitions and escalation rules before migrating |
| CMDB and impact analysis | Fully customizable CMDB with graphical impact analysis | Confirm how many CI and relationship types you rely on |
| Asset inventory and discovery | Inventory discovery depth is not a native iTop feature; plan a separate discovery tool or import | Confirm asset unit usage and discovery agents in your plan |
| CSV import and data consistency audits | CSV import and data consistency audits are listed in the iTop README | Confirm which fields your XML account export and ticket CSVs contain |
| Data synchronization | Data synchronization for federation is listed in the iTop README | Not applicable to a single Freshservice tenant; confirm any integrations you use |
| Licensing | Community free for up to 10 agents; Atelier up to 50 agents; Forge above 50 agents, per Combodo | Confirm your current per-agent plan and add-on costs from your contract |
| Hosting and commercial support | Available on premises or as SaaS; commercial support, training and consultancy from Combodo | Confirm Freshservice data center region and support tier in your contract |
Where ITSM data lives under Freshservice and iTop
Both products hold the same core records: tickets, configuration items, assets and contracts. What changes is who runs the database, who holds administrative keys and how a copy of the data leaves the system. The cards below cover those decisions in the order a CISO or IT lead usually reviews them.
Data location and hosting model
Freshservice is delivered as a SaaS service, and its account data sits in the vendor's environment. iTop can be run on premises in your own data center or cloud account, or consumed as SaaS from Combodo, which is a separate hosting decision with its own contract. Confirm the hosting region, subprocessors and where backups are stored for whichever option you choose, because these answers drive your data residency position.
Administrative access to the database
On a self-hosted iTop, your team or DeployOpen holds root access to the MySQL or MariaDB server, the web tier and the configuration files, so access reviews and privileged logging are yours to design. With Freshservice, administrators work through the application and the vendor operates the platform beneath it. Write down who can reach the database, who can change the data model and who can approve those changes.
Backup and recovery ownership
When iTop is self-hosted, the database, attachments and configuration backups are your responsibility, including restore testing and retention periods. Confirm with Combodo what its SaaS tier backs up and how restores are requested before you rely on it. Freshservice backup and recovery terms belong in its contract and service documentation, so ask for the recovery point and restore process in writing.
Full export from Freshservice
Freshservice account administrators can export the full service desk from Admin, Account, Export. The export arrives as XML at the registered agent email address, which makes the mailbox that receives it a sensitive store to protect. Plan a scheduled export, decide where the file is kept and test that it can be parsed before you rely on it as an exit path.
Audit evidence and compliance preparation
Compliance readiness means showing that access, change and backup controls work as described, with records to prove it. DeployOpen prepares systems, controls and evidence for an assessment, such as configuration baselines, access reviews and change logs. Independent auditors and certification bodies issue any attestation or certification, so ask your auditor which evidence they will sample before the work starts.
Data sync and export from iTop
iTop offers CSV import, data consistency audits and data synchronization for federation, so records can move in and out without a vendor ticket. Test the export format against your reporting needs and confirm that attachments, history and relationships are covered by the method you choose. These paths give you more direct control, but they need an owner who can run them.
Which iTop edition fits your agent count
Combodo offers iTop Community free for up to 10 agents, available on premises or as SaaS. This tier fits small IT teams that want a configurable CMDB, incident and change management, and SLA rules without a license fee. Licensing scope is the main constraint: the agent limit is the boundary, so a team that expects to grow past ten agents should plan the move to a paid edition before it reaches that point, not after.
- Licensing scope: Free use for up to 10 agents, counted against the people who work tickets, not every requester.
- Commercial support: Combodo sells support, training and consultancy separately, so a Community deployment depends on your internal skills or a third party you hire.
- Hosting: Running it on your own servers means you carry patching, backups and upgrades yourself.
- SaaS option: Available, but you pay the provider for hosting and operations and still own your configuration choices.
- Extensions: Extensions come from the iTop Hub, so check each one's license and maintenance status before you depend on it.
Confirm the current agent definition and any feature limits with Combodo before you commit to this tier.
Atelier covers up to 50 agents and is the middle tier, available on premises or as SaaS. Teams in this band usually have several service desk groups, separate change approvers and a larger asset base, so the question shifts from whether iTop fits to how much outside help and hosting you want. The price and terms are set by Combodo, so get them in writing for your exact agent count.
- Licensing scope: Covers up to 50 agents, which typically includes both fulltime and occasional ticket handlers in your count.
- Commercial support: Combodo support, training and consultancy are relevant here, especially for CMDB data model changes and SLA design.
- Hosting: On premises keeps data in your environment but leaves you with database tuning and backup work.
- SaaS option: Shifts server operations to Combodo, which may suit teams without a platform group.
- Upgrades: Plan testing time for each iTop release, since data model changes affect custom modules.
Ask Combodo how agents are counted for your roles and whether support levels differ between on-premises and SaaS.
Forge applies to more than 50 agents and is the top tier, also available on premises or as SaaS. Larger organizations in this group often run iTop as a federated CMDB, with data synchronization between instances and multiple business units relying on the same service catalog. Here the edition decision is tied to governance, change control and who operates the platform, so it deserves a formal scope document rather than a quick license comparison.
- Licensing scope: Covers more than 50 agents, so the exact count and any federation or multi-instance arrangement must be agreed with Combodo.
- Commercial support: Expect to need Combodo support or a partner for performance tuning, database sizing and integration work.
- Hosting: On premises gives full control over residency and network placement, but needs a dedicated operations team.
- SaaS option: Can reduce operational load, but review where data is stored, who can access it and how exports work at exit.
- Sizing: Combodo's requirements guidance separates small all-in-one servers from larger installations with separate web and database servers.
Request a written quote tied to your agent count, hosting model and support scope before you plan the rollout.
What self-hosting iTop costs beyond the license
The license line is the smallest part of the comparison, so start by splitting costs into one-time and recurring. On the Freshservice side, the recurring cost is the per-agent subscription plus asset unit packs, which Freshservice sells in addition to the 100 units included per plan. On the iTop side, the Community edition is free for up to 10 agents, and the paid Atelier and Forge editions, available on premises or as SaaS, are priced by Combodo. Ask Combodo for a written quote for your agent count and deployment model, and confirm whether support, training or consultancy is quoted separately from the license.
Self-hosting adds components that are paid for in staff time or a provider invoice. Server and database hosting is recurring, and sizing depends on your ticket volume and console users. Combodo's requirements page 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, with separate web and database servers at larger scale. Someone must also administer PHP 8.2 to 8.4, MariaDB 10.6 to 11.8 (preferred over MySQL 8 for performance), and GraphViz, and handle backups, upgrades and security patches. Those tasks are staff time that recurs for the life of the system, whether it is an internal team or an implementation partner on retainer.
One-time work is front-loaded: migration from the Freshservice XML export, data model design, CSV import mapping, rebuilding SLAs and change workflows, and initial hardening. Extensions from the iTop Hub may save build time, but each one needs a review for maintenance, licensing and upgrade compatibility before it goes into production. Ask any implementation quote for a fixed scope covering these items, the expected acceptance tests, and what happens to the data model when iTop releases a new version. Also ask who pays for upgrade testing, backup restore drills and the first year of support, since those decide whether the recurring cost is predictable.
What running iTop asks of your team
Running iTop yourself means owning a PHP and database stack, a sizing decision, upgrades between release lines, and every extension you add. Freshservice hides most of this behind its SaaS service, so the work below moves to your side of the contract. Each card names what an internal team can usually handle and what is worth buying help for.
Platform requirements
iTop 3.3.x requires PHP 8.2 to 8.4 and GraphViz for impact diagrams. It supports MySQL 5.7 or later and MariaDB 10.6 to 11.8, with MariaDB preferred and MySQL 8 discouraged for performance reasons. Your team can usually manage the packages and patch cycle. Confirm the PHP and database versions your operating system supports before you pick a base image, because version drift here is the most common cause of a failed install.
Server sizing decisions
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 separate the web and database servers, with up to 8 vCPU and 16 GB each. Size from your real ticket volume and console user count, not from your Freshservice agent licenses. Ask your database administrator to review the layout before go-live, since CMDB imports and impact analysis queries grow with the data.
Upgrades between 3.2.x and 3.3.x
iTop 3.3.0 was published on September 15, 2026, and 3.2.3-3 on October 16, 2026. Moving between release lines changes the data model, extensions and PHP requirements, so plan each upgrade in a staging copy first. Your team can run routine patch upgrades. A jump across a major line, or an upgrade with heavily customized modules, is a good point to bring in Combodo or an implementation partner with a written scope.
Backup and restore testing
Backups cover the database, the iTop configuration folder and any uploaded attachments. A backup that has never been restored is not a backup. Schedule a restore into a separate host at least quarterly, then log the time it took and any manual steps. Freshservice's export is a single account-level file you request from the admin console, so iTop's backup routine is an operational duty your team owns from day one.
Extension governance
Extensions from the iTop Hub add features, but each one changes the data model or the user interface and must be tested against your iTop version. Keep a register of installed extensions, their versions and their owners, and test each one in staging before any upgrade. Decide early which customizations your staff can build and which need Combodo or partner review, since a custom module that breaks at upgrade time is costly to fix.
Support and training
Combodo sells commercial support, training and consultancy for iTop, and offers the licensed editions on premises or as SaaS. Internal teams can handle daily administration and helpdesk configuration. Ask Combodo for a written scope covering response expectations, upgrade assistance and training for administrators before you choose between self-support and a paid edition, because the Community edition covers up to 10 agents.
Moving from Freshservice to iTop: the steps of a migration
The sequence turns a Freshservice account export into a tested iTop data model, with workflows, SLAs and change processes rebuilt deliberately rather than carried over by accident. Each step closes with a check that tells the team whether it can move on.
Export the full Freshservice account
A Freshservice account administrator opens Admin, Account, Export and requests the full service desk export. The XML file is delivered to the registered agent email address of the administrator, so confirm that mailbox is controlled by your team and is not tied to a departing employee. The export carries ticket and account data, but it is not a complete configuration export: workflows, automations, SLA policies and change approval rules must be documented separately from the admin screens. The step is done when the file is stored in a restricted location, its checksum is recorded, and the team has confirmed the record counts against what the admin console reports.
Inventory what must be rebuilt
Work with the service desk lead and the CMDB owner to list every item that the export does not carry: ticket categories and custom fields, assignment groups, asset types and relationships, SLA targets, escalation rules, change types and approval paths, and the service catalog. Record which Freshservice automations are business-critical, such as routing, notifications and asset lifecycle triggers, and which can be retired. Ask Freshservice support or your account contact to confirm which configuration exports, if any, are available for your plan. The step ends with a signed-off inventory that maps each item to an owner and a target state in iTop.
Design the iTop data model
Using the inventory, the iTop administrator decides how classes, lifecycle states, contacts, teams and relationships will be configured. Typical decisions include which asset classes replace Freshservice asset types, how configuration items relate to services and contracts, and how the ticket classes map to incidents, service requests and changes. iTop's model is customizable, so these choices should be written down before data moves, because changing them later means re-importing. The step is complete when a design document has been reviewed by the service owner and a test instance reflects it.
Convert tickets and assets into CSV import files
Transform the XML export and any ticket or asset CSVs into files that match the iTop CSV import format for each class, with stable external keys so that relationships resolve on import. Map Freshservice requesters, agents and groups to iTop contacts, teams and users, and decide whether closed tickets older than a set retention point are archived instead of imported. Keep the conversion scripts under version control so each run is reproducible. The step is complete when the files import cleanly into a staging instance and the row counts reconcile with the source export.
Run data consistency audits
Load the converted data into a staging iTop instance and run its data consistency audits to find orphaned records, broken relationships, duplicate assets and missing mandatory fields. Compare a sample of tickets and assets, chosen by the service desk lead, against the original Freshservice records, including conversation history and attachments. Document each defect, its cause and the fix, then re-run the conversion rather than editing records by hand. The step is done when audits return no unresolved errors and the sampled records match the source on status, owner, timestamps and key relationships.
Recreate SLAs and change workflows
Build the SLA definitions, escalation rules, notification templates, change types and approval steps in iTop according to the inventory from the second step. Test each rule against sample tickets and changes, including the boundary cases where a target is breached or an approval is rejected. Verify that reports and dashboards expose the same measures the business uses today, and document any automation that Freshservice performed and iTop does not, so that a manual procedure replaces it. The step is complete when each rule has a passing test and a named owner.
Pilot with a subset of agents
Select a small group of agents and a bounded set of services, then run live work in iTop while Freshservice stays available for reference. Collect feedback on the agent interface, search, assignment and reporting, and log each gap against the rebuilt inventory. Check that email integration, user authentication and any integrations to monitoring or directory systems behave as expected in your environment. The pilot is finished when the agreed exit criteria are met and the service desk lead signs off on the defects that remain open.
Cut over and retain the export
Schedule the final conversion, freeze Freshservice changes for the cutover window, import the latest data, and repeat the audits and sample checks before opening iTop to all agents. Update intake channels, redirect requesters and retire Freshservice automations once their iTop equivalents are confirmed. Keep the signed export, the conversion scripts and the audit logs under your retention policy, and confirm with Freshservice how long the account remains accessible before you cancel. The step is done when all agents work in iTop, the audit results are archived, and the old platform is read-only or closed according to your decision.
Questions buyers ask before choosing iTop over Freshservice
How much effort does a move from Freshservice to iTop take?
The effort depends mostly on how much of your Freshservice configuration you need to rebuild, not on the size of the export file. Three things drive it: the number of asset classes and relationships you keep in the CMDB, the number of SLAs, approval paths and change workflows you recreate, and how clean your existing data is. Freshservice's full account export arrives as XML, so it has to be converted into the CSV import format iTop uses before anything loads. Each conversion step, validation pass and workflow rebuild adds work. Ask any implementation partner for a written scope that lists these items individually, so you can see where the effort sits before you agree to a plan.
Can our team run iTop without outside help?
Many IT teams can run iTop day to day with internal staff, but the first build and the data model usually need specialist skills. iTop's data model is customizable, so administrators must understand how classes, lifecycles, SLAs and notifications interact before they change them. The software stack also requires PHP 8.2 to 8.4, a supported MySQL or MariaDB version, and GraphViz, and someone has to own patching, backups and upgrades. Combodo sells commercial support, training and consultancy for iTop, which is one route. Decide early which tasks your staff will own permanently, which they will only learn, and which you will contract out.
What do we need to provide for an iTop migration project?
The project needs named data owners, administrator access and a decision-maker who signs off the data model. Data owners confirm which Freshservice assets, contracts, services and ticket histories are still valid and which should be archived. Administrator access to Freshservice is needed to run the full export, and access to the target iTop server is needed for imports and configuration. The data model sign-off matters most: asset classes, relationships, SLA definitions and change approval steps should be written down and approved before data is loaded. Without that agreement, teams often rework the model after go-live, which costs more than the design work would have.
How long does a migration to iTop take, and what sets the duration?
No duration is fixed in advance, and the schedule depends on the scope you agree in writing. The main factors are the number of workflows and SLAs to recreate, the volume and quality of asset and ticket data, the number of integrations and the availability of your data owners for review. Hosting choices also matter, since an all-in-one server suits smaller installations, while larger ones need separate web and database servers. Combodo's requirements page 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 servers of up to 8 vCPU and 16 GB for larger installations. Ask for a timeline that breaks the work into discovery, data model, import, testing and cutover.
Does iTop replace Freshservice's asset units?
iTop does not use Freshservice's per-unit asset model, so you should not expect a one-to-one swap. iTop's CMDB is a configurable data model where you define the classes of objects you track and the relationships between them, and it has no built-in per-asset license. Freshservice sells asset management units in packs, so moving away removes that fee, but you still need a plan for discovery. iTop's README describes a CMDB, graphical impact analysis and data consistency audits, but asset discovery is a separate concern. Confirm with Combodo or your partner how inventory data will arrive, whether through CSV import, a synchronization connector or an extension from the iTop Hub, and test that path with your own data.
What does the 10-agent Community limit mean in practice?
The iTop Community edition is free for up to 10 agents, so a team with more than 10 people working tickets must move to 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. Count agents by the people who work tickets, not by everyone who views the console, and check the current terms with Combodo before you commit. Growth in agent count is the main cost driver, so model headcount for the next few years alongside the license tier. Community use is also an evaluation route, but production support and extensions may need a paid plan.
How does SaaS iTop from Combodo differ from self-hosting?
SaaS iTop from Combodo means Combodo runs the platform and you rely on their hosting, upgrades and operations. Self-hosting means your team, or a partner you choose, runs iTop on servers you control, including the web tier, the MySQL or MariaDB database, backups and patching. The choice affects data location, who can reach the database, how quickly you can apply security fixes and who pays for infrastructure. Self-hosting shifts recurring operating work to your side, while SaaS shifts it to the vendor under its service terms. Ask Combodo for its hosting locations, backup approach and contractual terms, and compare them with your own data residency and audit requirements.
Which iTop version should we plan around?
Plan around the current supported 3.3.x line, and confirm the exact release you will deploy before you build. iTop 3.3.0 was published on September 15, 2026, and 3.2.3-3 on October 16, 2026, according to the Combodo release page. Version choice determines the PHP and database versions you must support, so check the software requirements before you provision servers. Write the chosen version into the project scope so that later upgrades are planned and tested rather than discovered during a patch cycle.
How DeployOpen works on this
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Freshservice to iTop move, the work starts with a written scope that fixes what the CMDB, service management and migration cover before any build begins.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts
- Scope covers which Freshservice asset units, tickets, SLAs and change workflows move to iTop
- Confirm iTop edition, agent count and whether hosting is on premises or SaaS from Combodo
How we build
- Install iTop on MySQL or MariaDB with the PHP and GraphViz versions Combodo's requirements list
- Design the CMDB data model, impact analysis views and SLA rules to match your service catalog
- Convert the Freshservice XML export and ticket CSVs into iTop's CSV import format and test with samples
How we hand over
- Deliver documentation for the data model, import procedures, configuration and operational runbooks
- Run data consistency checks and reconcile imported assets and contracts against your source records
- Provide training and a cutover checklist so your agents and administrators can run iTop without us
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- Plan iTop version upgrades and extension changes, including extensions distributed through the iTop Hub
- Keep backups, hardening and access reviews in your own environment on an agreed schedule
