Open-source alternative to ServiceDesk Plus asset management: the short answer
GLPI with GLPI Agent covers asset discovery and inventory inside one ITSM platform, while Snipe-IT fits teams whose main need is checking assets out to people and tracking their lifecycle. If your ServiceDesk Plus Professional renewal is priced by asset count and you need a self-hosted replacement, GLPI is the closer match when asset data must feed incident, problem, change and service level management in the same tool. GLPI is free software under GPL-3.0, so the recurring cost moves from a per-asset license to your own servers, storage, database administration, backups and staff time. GLPI Agent collects hardware and software inventory, performs network discovery and sends the results to GLPI, and it runs on Windows, macOS and Linux. Snipe-IT, licensed under AGPL-3.0, is built around who holds which laptop, purchase dates for depreciation and software license seats, and it is a lighter choice if you do not need a service desk on the same platform.
Choosing between them is a question of where asset data needs to live. If you pick GLPI, you can keep the rest of the ServiceDesk Plus suite in place for now and move asset records first, or move everything in one project. If you pick Snipe-IT, expect to keep request handling elsewhere and connect the two through its JSON REST API. Either way, confirm the gaps against your own environment before you commit: ask which discovery protocols and endpoint types your network requires, whether your ManageEngine scan coverage matches what GLPI Agent will collect on the same machines, how check-in and check-out approvals must be recorded for audit, and whether your identity provider is supported for login. GLPI supports LDAP, IMAP and other external authentication methods, and Snipe-IT supports LDAP sync and SAML, but your directory and identity setup should be tested rather than assumed.
Treat this page as a starting point for a cost review, not a verdict. Ask any implementation partner for a written scope that lists which asset types, discovery ranges, users and integrations are in and out, then compare that scope with your current ServiceDesk Plus configuration. Check the GLPI system requirements for PHP and MariaDB or MySQL versions against your hosting standards before sizing servers, and confirm which Snipe-IT and GLPI features your asset reports depend on. The cost comparison and the migration steps are covered in the sibling sections of this page, so use this summary to decide which product to evaluate first.
Which open-source option covers each ServiceDesk Plus asset capability
This table maps the main ServiceDesk Plus asset capabilities to GLPI, GLPI Agent and Snipe-IT, with a note on where each option is strong or thin. Read the cells as a starting point: the ManageEngine module details, such as scan scheduling depth and agent management, need to be checked against your own licence and configuration before you decide.
| Capability | GLPI with GLPI Agent | Snipe-IT | What to confirm in ServiceDesk Plus |
|---|---|---|---|
| Hardware and software inventory | GLPI Agent collects hardware and software inventory and sends it to GLPI on Windows, macOS and Linux | Not a discovery tool; assets are recorded manually, imported by CSV or created through the REST API | Which OS and device types your ManageEngine agents cover today |
| Network discovery | GLPI Agent performs network discovery and inventory feeding GLPI | No network scanning capability described in the supplied documentation | Scan ranges, schedules and how discovered devices are merged with existing records |
| Scan scheduling and agent management | Agent deployment and scheduling depend on your configuration; confirm the depth you need for central control | Not applicable | Scheduling granularity, agent update control and remote management features in your ManageEngine edition |
| Asset lifecycle and depreciation | Asset records and status tracking in the inventory; confirm depreciation handling against your finance rules | Purchase dates support depreciation tracking and lifecycle status | Depreciation methods, schedules and how they feed financial reports |
| Check-out to people | Assignment of assets to users is supported through the inventory; confirm the check-out workflow you need | Checks out assets, licenses and accessories to people | Whether check-out requests and approvals are part of your current process |
| Consumables and components | Limited; component records depend on how the inventory is modeled | Covers consumables such as toner and components such as RAM and hard drives | Whether you track consumables stock levels and reorder points |
| License tracking and contracts | Contract management is included, and GLPI tracks software from inventory | Tracks software licenses, with purchase records and seat assignment | Compliance rules, true-up reports and contract renewal alerts you rely on |
| CMDB links | CMDB relationships between configuration items are part of GLPI's scope | Not a CMDB; relationships are limited to assignment and location | Which relationships ServiceDesk Plus maps and whether you need them for change impact |
GLPI or Snipe-IT: when each option fits and where it stops short
ServiceDesk Plus Professional combines asset discovery, IT asset management and ticketing in one product. In open source, the choice is usually between GLPI, which covers inventory and ITSM together, and Snipe-IT, which focuses on asset lifecycle and check-out. The cards below set out the fit and the gaps for each.
GLPI with GLPI Agent
GLPI covers asset inventory and ITIL linkage in one database. GLPI Agent collects hardware and software inventory from Windows, macOS and Linux endpoints, performs network discovery and sends results to GLPI, which can link assets to tickets, changes and contracts. The package is GPL-3.0 with no license fee. Check how your discovery scope, scan schedules and agent deployment will be managed, and confirm that agent coverage matches your endpoint mix. Teclib' offers paid GLPI Network subscriptions and support tiers, so budget for those separately if you need them.
Snipe-IT for check-out workflows
Snipe-IT is built around who holds which asset. It tracks check-out and check-in of laptops, licenses and accessories to people, handles consumables and components, and records purchase dates for depreciation. It is AGPL-3.0 licensed, supports LDAP sync and SAML login with providers such as Entra ID and Okta, and exposes a JSON REST API. It does not replace an ITSM ticketing module, so incidents, changes and approvals must come from another system. Check whether AGPL obligations apply to any modifications you make before you deploy.
Where GLPI stops short
Discovery depth and maintenance are the main gaps to test. Confirm that GLPI Agent covers the operating systems, network devices and remote ESX hosts in your estate, and compare its reporting with the ManageEngine module against your own asset reports. Plan for ongoing work on the PHP and database stack, plugin reactivation after major updates and backup of the config keys. Teclib' hosted and support options are paid, so ask for those figures in writing rather than assuming them.
Where Snipe-IT stops short
Snipe-IT covers lifecycle tracking, not service delivery. Discovery of unmanaged devices is not its job, so you will need another source for network inventory or an import process that keeps records current. Ticketing, change approval and SLA reporting also sit outside it. If you run Snipe-IT alongside an ITSM tool, plan integration work through the REST API, define which system owns each asset record, and set a sync schedule so check-out data and tickets agree.
Running both tools together
Using GLPI and Snipe-IT together means two data owners. A common split is GLPI for discovered inventory and ticket links, and Snipe-IT for people-facing check-out and depreciation. Illustrative example: a laptop discovered by GLPI Agent is assigned in Snipe-IT and the assignment is pushed back to GLPI through the API. Decide the system of record for serial numbers and owners before migration, test duplicate handling, and ask your implementation partner to document the sync and its failure modes.
Hosting and runtime checks
Both tools run on a LAMP-style stack that you operate. GLPI requires PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later for the current release, and its document root must point at the public directory. Snipe-IT requires PHP 8.2 or later and below 8.6, with MySQL 5.7+ or MariaDB, and offers a Docker image. Confirm your server build, backup routine and patch window with your platform team before choosing a version.
How GLPI Agent discovery and inventory feed GLPI
GLPI Agent is the component that moves asset data from your machines and networks into GLPI. It is the successor of FusionInventory Agent, runs on Windows, macOS and Linux, and collects hardware and software inventory from each device. The same agent family also performs network discovery and inventory, deploys packages and can inventory remote ESX hosts, then sends the results to GLPI. Before deployment, decide which of these functions you need. Inventory on managed endpoints is one project. Network discovery across printers, switches and unmanaged devices is a second project with its own scan scope and its own risks. Confirm the exact task types and their configuration in the GLPI Agent documentation for the agent version you plan to run.
Plan four things before rollout. First, the deployment method: agents can be pushed by your existing endpoint management tooling, installed through a manual or scripted process, or placed in a golden image, and the choice determines how you track agent versions afterward. Second, scan scope: define the IP ranges, subnets and remote ESX hosts that discovery may touch, and agree the scan windows with network operations so that discovery traffic does not disrupt production systems. Third, server connectivity: every agent must reach the GLPI server over the network path you have approved, so verify proxies, firewall rules and TLS certificates for each site and each remote segment before you count an agent as deployed.
Fourth, reconciliation. Discovered devices will not automatically match the assets already in GLPI, so decide the matching rules in advance: which identifier wins (serial number, hostname, MAC address or inventory tag), who reviews duplicates, and how retired hardware is marked so that it stops appearing as active. Run a pilot on one site, compare the imported records with your current asset register, and document the exceptions. Those exceptions, and the owner for each, are the evidence an auditor or internal reviewer will ask to see.
Running the asset module beside the rest of ServiceDesk Plus
Many teams will not move every ServiceDesk Plus function at once. Keeping tickets in ServiceDesk Plus while GLPI or Snipe-IT holds asset records creates a split that needs clear ownership, a shared identity source and a realistic count of what two systems cost to run.
Keep tickets, move inventory
ServiceDesk Plus can keep handling requests while GLPI Agent feeds hardware and software inventory into GLPI. Decide which system is the record for asset identifiers, serial numbers and status before any sync is built. Confirm whether your ServiceDesk Plus edition can import or query the asset data you need for tickets, since this split needs a deliberate integration step.
Keep assets, move check-out
Snipe-IT can handle check-out of laptops, licenses and accessories while ServiceDesk Plus keeps the asset module for discovery and lifecycle records. Two asset registers will drift unless one is named the source of truth for each item. Ask which system owns purchase, depreciation and disposal data before users start checking items out in the new tool.
Directory login for each tool
GLPI tries authentication against its internal database first, then LDAP, then IMAP and other external methods such as REMOTE_USER, in that order. Snipe-IT's LDAP sync imports and updates users from LDAP or Active Directory and lets them log in with directory credentials, falling back to local accounts. Snipe-IT also supports SAML with providers such as Entra ID and Okta. Check that leavers are disabled in both tools when they leave the directory.
Linking assets to tickets and users
Assets only help incident work when a ticket points to the right device and the right person. Map user identifiers from the directory consistently across both tools, and agree which field matches a device to a requester. Test the link with a sample of tickets before retiring any manual lookup step, because mismatched user records are a common cause of wrong asset assignments.
Cost of two systems
Running two systems means two sets of upgrades, backups, server hosting and administrator time, plus the integration you maintain between them. Snipe-IT's self-hosted software is free to use, and GLPI has no license fee, but staff time and infrastructure still recur. Ask any quote to separate integration build, ongoing sync maintenance and the ServiceDesk Plus licenses you still pay for the tickets module.
Moving asset records, scans and check-out history
This sequence moves asset records, user assignments and scan data from ServiceDesk Plus into GLPI or Snipe-IT, with discovery running in parallel until the new inventory is trusted. The result is a target inventory that matches the old one on hardware, licenses and who holds what, before the old scans are switched off.
Export asset and user data from ServiceDesk Plus
The ServiceDesk Plus administrator pulls asset, user and assignment data using query reports exported to CSV, or direct database access on on-premises installs. The team that owns the inventory should confirm which asset types, custom fields and historical check-out records the export actually includes. Done means each export file has a row count the administrator has checked against the ServiceDesk Plus asset list, and the team has a written inventory of which fields were exported. The sibling export page covers the report steps in detail.
Build the target schema in GLPI or Snipe-IT
The implementation team maps each exported field to a GLPI asset type (computers, monitors, network equipment, software licenses) or to a Snipe-IT model, category, manufacturer, status label and custom field. Snipe-IT suits check-out tracking of laptops, licenses and accessories, while GLPI suits a broader inventory tied to tickets and contracts. Done means a written field map exists, and a test instance has one sample record of each asset type that the reviewers have accepted.
Import records with the target's import tools
The team imports the mapped files into a non-production instance using the target's import functions, then repeats the import on a clean copy so the process is repeatable. Confirm for each field whether it survives the import, including serial numbers, purchase dates, warranty fields, assigned users and attachments, because some ServiceDesk Plus data may land in notes or be dropped. Done means a field-by-field comparison shows which data arrived intact and which needs manual work.
Authenticate users against the directory
Before check-out assignments are validated, user accounts must match the directory. GLPI authenticates against its internal database, LDAP, IMAP or external methods in that order, and Snipe-IT can sync users from LDAP or Active Directory and fall back to local accounts. The identity team confirms which directory is authoritative and that imported user records match it. Done means each assigned user in the test instance resolves to a single directory account.
Deploy GLPI Agent alongside existing scans
Install GLPI Agent on a pilot group of Windows, macOS and Linux endpoints while ServiceDesk Plus scans keep running. GLPI Agent sends hardware and software inventory to GLPI and can run network discovery, so the team can compare what each source reports for the same device. Done means the pilot devices appear once in GLPI with hardware and software data, and the team has a list of differences from the ServiceDesk Plus record for each device.
Reconcile duplicates and validate check-outs
Duplicates usually appear when the same device is found by both the old scans, the new agent and discovery, or when a device is recorded under two names. The asset owner merges records by serial number and hostname, then checks each open check-out against the person who currently holds the device. Done means a duplicate count is zero for the pilot set, and the asset owner has signed off on a sample of check-out assignments for each department.
Cut over scans and retire the old inventory
Once the pilot reconciliation is accepted, the team extends GLPI Agent to the remaining endpoints in waves, disables ServiceDesk Plus scan schedules device group by device group, and keeps a read-only export of the old data for audit and reference. Done means every endpoint reports to the new inventory, the old scan schedules are disabled, and the archived export has been stored in a location the compliance owner controls. Ask the implementation partner to confirm the retention terms for that archive in writing.
What does replacing ServiceDesk Plus asset management cost and require?
What does it cost to replace ServiceDesk Plus asset management with open source?
The software license is zero for self-hosted GLPI and self-hosted Snipe-IT, so the cost sits in the components around it. Snipe-IT's pricing page states that its self-hosted software is and always will be free, and GLPI is distributed under GPL-3.0. Budget for the server and database hosting, storage, the time to build discovery and import data, ongoing operations such as backups and upgrades, and any paid support. If you want a managed option, Snipe-IT's hosted plans start at $399.99 per year, and GLPI Network lists 19 euros per user per month for its public cloud. Ask any quote to separate one-time migration work from recurring operations and support.
How long does an asset management migration take, and what drives the timeline?
No fixed duration applies to every estate, so the timeline depends mostly on the work you must do. The main drivers are the number of assets, how many sites and network segments discovery must cover, how clean the existing ServiceDesk Plus data is, and how many custom fields, asset types and reports must be recreated. Duplicate records, missing owners and inconsistent asset tags add time at the import stage. Scan scope matters too: deploying GLPI Agent to laptops and servers is faster than mapping network devices that need credentials and tuning. Ask any proposal to break the timeline into discovery, data cleanup, import, validation and cutover.
Can our own team replace ServiceDesk Plus asset management without outside help?
A small estate with one site and a team comfortable with Linux, PHP and databases can often do it in house. GLPI Agent runs on Windows, macOS and Linux and sends hardware and software inventory to GLPI, which keeps the endpoint side simple. Multi-site network discovery is harder, because it needs correct scan ranges, credentials for network devices, and someone who can tune discovery so it does not flood the database with duplicates. Snipe-IT is simpler to run alone for check-out tracking, but it does not replace network discovery. Be honest about who will own patching, backups and upgrades after go-live.
What does the server and identity side of GLPI or Snipe-IT require?
You need a web server, a supported PHP version and a supported database, plus a directory connection if you want single sign-on or user sync. GLPI 11.0 requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6, and its newer README lists PHP 8.3 or later with MariaDB 10.11 or MySQL 8.0. GLPI's document root must point to its public directory with URL rewriting. Snipe-IT requires PHP 8.2 or later and below 8.6, MySQL 5.7+ or MariaDB, and Apache with mod_rewrite or IIS with URL Rewrite. For identity, Snipe-IT supports LDAP or Active Directory sync and SAML providers, and GLPI authenticates against its database, LDAP, IMAP or REMOTE_USER. Confirm the versions against the current documentation before you build.
What should we back up and plan for before upgrading GLPI?
Back up the database, the application files and the config directory, including the glpi.key and glpicrypt.key files, before you touch anything. The GLPI update procedure replaces the application files and then runs php bin/console db:update. Since GLPI 11.0, plugins are suspended after a new version is detected and must be reactivated, so plan time to test each plugin after a major update. Losing the key files can make encrypted data unreadable, so store them separately from the server. Schedule these steps as recurring operations work, because they repeat with every release.
When should we bring in an implementation partner for asset management?
Bring in a partner when the discovery design, data migration or integration work is larger than your team can absorb without disrupting daily service. DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted platforms inside your own infrastructure, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. Good triggers include multi-site discovery, integration with directory and procurement systems, audit evidence needs, or a cutover that cannot tolerate gaps. DeployOpen does not publish a price list, so ask for a quote built from the written scope.
Which costs stay the same after go-live, and which shrink?
Recurring costs usually include hosting, storage, backups, patching and upgrade effort, and any support contract you choose. One-time costs include the migration, discovery design, data cleanup, report rebuilding and user training. Your ongoing burden shrinks when agent deployment is automated through your endpoint management tooling and when asset records are clean from the start. It grows when the estate is large, when many custom fields or plugins must be maintained, or when you run several environments. Ask vendors and partners to show these lines separately so you can compare them with your current ManageEngine subscription.
Where open-source asset tools need extra work
The first thing to test is whether GLPI's discovery and inventory depth matches what your ManageEngine setup does today. GLPI Agent collects hardware and software inventory, performs network discovery and inventory, handles package deployment and runs remote ESX inventory, so the feature list overlaps. What you must confirm is how far each of those matches your current scan schedules, credential handling, agent rollout and reporting. Run a pilot across a representative subnet set and one Windows, macOS and Linux group, then compare the asset records GLPI produces against your ServiceDesk Plus data, field by field. Ask Teclib' or your partner which discovery methods and scheduling options your version exposes, and write down every report you rely on today that has no direct GLPI equivalent.
GLPI's upgrade procedure is the step most likely to collide with your change process. The documented sequence is to back up the database, the files and the config directory, including glpi.key and glpicrypt.key, replace the application files, and run php bin/console db:update. Since GLPI 11.0, plugins are suspended when a new version is detected and must be reactivated after major updates, so every plugin you depend on needs a named owner and a post-upgrade check. Lost encryption keys make restored data unreadable, so key backup belongs in your recovery test, not just the database dump. Build this into a standard change record and rehearse it on a copy before the first production upgrade.
Snipe-IT covers check-out well: it tracks assets, licenses and accessories checked out to people, consumables and components, and it can use LDAP or SAML for login. It does not replace the ITSM workflow. Incidents, problems, change approvals, SLAs and service catalog items are outside its scope, so if you choose it for hardware lifecycle, the ticketing side must live elsewhere and the two need an integration you design and test. Confirm with the vendor and in a pilot which API fields and actions you need for that link, how check-out approvals are recorded, and whether audit history meets your retention rules. Treat the split as a decision you document, not a gap you discover after cutover.
How DeployOpen scopes and delivers an asset module replacement
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For an asset module replacement, that means agreeing in writing what GLPI or Snipe-IT must cover, building it on your infrastructure, and handing over a platform your own team can run.
How we scope
- Inventory which ServiceDesk Plus asset data, reports and integrations your teams actually use today
- Decide whether GLPI Agent discovery, Snipe-IT check-out, or both fit your asset types and workflows
- Agree deliverables, timelines and exclusions in a fixed-scope written statement before work starts
How we build
- Deploy GLPI or Snipe-IT on your own servers with the web server, PHP and database versions confirmed against current requirements
- Connect directory sources such as LDAP or SAML so asset owners sign in with existing accounts
- Test agent inventory and discovery results against a sample of known devices before wider rollout
How we hand over
- Document configuration, data mappings, field definitions and the reconciliation steps used during migration
- Train administrators on check-out, depreciation, license tracking and the update procedure, including backup of configuration keys
- Deliver runbooks that state which asset features remain manual, so gaps against the ManageEngine module are visible
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- Agree the support scope, response expectations and upgrade cadence in writing with your team
- Confirm with the vendor and your own environment which features your edition or version provides
