Open-source ServiceNow IT asset management alternative

Open-source ServiceNow IT asset management alternative: the short answer

If your ServiceNow IT asset management renewal is forcing a decision, the short answer is that GLPI can cover hardware and software inventory, contracts and financial data, and Snipe-IT can cover check-in and check-out of laptops, licenses and accessories. GLPI is free under GPL-3.0 and collects inventory through GLPI Agent, which runs on Windows, macOS and Linux. Snipe-IT is licensed under AGPL-3.0 and tracks who holds which device, purchase dates for depreciation and software license assignments. Neither product is a one-to-one copy of ServiceNow's asset module, so the migration will involve mapping and some rebuilding rather than a direct import. The main gap is not feature depth but where asset records should live. If your ServiceNow assets are tied to incidents, changes and configuration items, keeping them inside GLPI lets the service desk and the inventory share one database and one set of relationships. If your asset team mostly needs a lightweight register for issuing laptops and tracking licenses, a separate Snipe-IT instance can be simpler, but you then have to keep the two systems in step, for example by agreeing which tool is the source of truth for asset status and ownership. Decide this before you export anything, because it determines your data model, your integrations and who administers each system. Before you commit, confirm three things with your own data: how many users need check-out rights, whether your identity provider must drive logins (Snipe-IT supports LDAP and SAML, and GLPI supports LDAP and external methods), and whether your ServiceNow export limits will leave gaps in software or contract records. Ask any vendor or partner to show how each system handles your largest asset categories in a test instance, and get the scope and deliverables in writing before the work begins.

Which open-source tool covers each ServiceNow asset capability

This table maps each ServiceNow asset capability to GLPI, GLPI Agent, Snipe-IT or a combination, and flags where the reader must confirm fit. Read each row as a question about your own estate: if a capability matters to your audit or finance team, check the named tool against it before choosing a split architecture.

Capability	Open-source coverage	What to confirm in your environment
Hardware inventory	GLPI inventory fed by GLPI Agent on Windows, macOS and Linux devices	Agent deployment reach across your device fleet, and whether unmanaged or offline devices need manual entry
Software inventory	GLPI Agent collects installed software, feeding GLPI's software catalog	How installed software maps to license entitlements, since reconciliation logic differs from ServiceNow Software Asset Management
Software license reconciliation	Partial: GLPI tracks licenses against contracts and installations, Snipe-IT tracks license seats	Whether your true-up rules, metric types and entitlement hierarchies can be reproduced, and who owns that logic
Contracts and financial data	GLPI contract management and financial fields on assets	Whether your purchase orders, cost centers and depreciation schedules must sync with a general ledger or ERP
Lifecycle and depreciation	Snipe-IT tracks purchase dates for depreciation; GLPI covers lifecycle states and contracts	Your depreciation method and approval workflow, and whether finance accepts the output as its system of record
Check-in and check-out of laptops, licenses and accessories	Snipe-IT covers checking assets, licenses and accessories out to people, plus consumables and components	Whether requesters, approvals and return reminders need to live in the same ticket as the incident or request
Discovery of network devices	GLPI Agent performs network discovery and inventory; it is the successor of FusionInventory Agent	Coverage of your network segments, SNMP settings and agentless devices, since this differs from ServiceNow Discovery
ServiceNow-specific reporting	GLPI reporting and Snipe-IT reports cover standard asset views	Whether dashboards, scheduled reports and cross-module metrics built in ServiceNow have an equivalent to rebuild

When GLPI, Snipe-IT or both fit your asset estate

GLPI keeps asset inventory, contracts and ITIL records in one system, while Snipe-IT tracks who holds which device, license or accessory. The right pattern depends on whether your asset records must drive service desk work or whether a dedicated check-in and check-out process is the bigger need.

GLPI as the single system

GLPI holds hardware and software inventory, contracts, and the incidents and changes that touch those assets in one database. Inventory arrives through GLPI Agent on Windows, macOS and Linux, so records stay current without manual entry. The trade-off is that a check-out workflow for loaned laptops is less direct than in a dedicated tool. Confirm how your team will record handovers and returns before committing.

Snipe-IT for check-in and check-out

Snipe-IT is built for tracking who has which laptop, which software license seat and which accessory, with purchase dates for depreciation. It covers consumables and components such as RAM and drives, which suits end-user device lifecycles. Its AGPL-3.0 license requires attention if you modify and offer the software to users over a network. Check that your legal team accepts that obligation before you customize it.

Directory sign-in for Snipe-IT

Snipe-IT can import and update users from LDAP or Active Directory and let them sign in with directory credentials, falling back to local accounts. It also supports SAML with providers such as Entra ID, Okta and Authentik. Decide early which identity source owns user records, because two sources can produce duplicate or orphaned owners. Confirm how local fallback accounts will be governed and reviewed.

Combined pattern with two systems

Running both tools lets GLPI own inventory, contracts and incident linkage while Snipe-IT owns assignment and handover. The cost is a second database, a second set of users and a sync or manual reconciliation step between them. Define which tool is the source of record for each field, such as serial number, owner and location, before any data load. Assign a named owner for the sync process.

Operating cost of each tool

Both products are free to self-host, so the recurring cost is infrastructure, patching, backups and staff time. Snipe-IT's hosted plans start at a published annual fee for email support and automated upgrades, which is a separate option from self-hosting. GLPI support can come from Teclib' or a partner. Ask any vendor or integrator for a written scope covering upgrades, backups and support hours before you compare totals.

Upgrade and plugin checks

GLPI 11.0 suspends plugins after a new version is detected, so each major upgrade needs plugin reactivation and testing before users return. Asset data in GLPI must be backed up together with the config directory keys, or restored data may not decrypt. Plan a test instance for every upgrade. Confirm that any plugin you rely on for asset workflows has a release for your target version.

Should asset records live in the service desk or a separate tool?

Keep asset records in the service desk when assets are tied closely to incidents, changes and configuration relationships. In GLPI, a laptop, server or licensed application can sit alongside its tickets, contracts, change history and CMDB links, so a technician opening an incident sees the affected hardware and its maintenance contract on the same screen. Snipe-IT becomes the better fit when the main work is high-volume check-in and check-out: onboarding batches of laptops, loaning accessories, tracking consumables and matching software seats to people. Many teams run both, but that choice should be made deliberately before data migrates, not after two systems disagree.

The main risk of a split is drift. If Snipe-IT holds the assigned user for a laptop and GLPI holds the asset that a ticket points to, the two records start to differ the first time someone reassigns a device in one tool and forgets the other. Agreed rules help: name one system as the owner of the asset tag, serial number and status, and decide which fields flow in each direction. Ask whether the integration is a scheduled export, an API sync built by your team, or a manual process, and who is accountable when the records conflict. Snipe-IT's REST API can push changes, but the synchronization logic is yours to design and test.

Before deciding, run a short test with real records: pick one asset class, check it out to a user in each tool, open an incident against it and confirm that the link, the history and the owner match. Ask DeployOpen or your GLPI partner to document the source of truth in writing, including who may change status and how a retired asset is closed in both systems. If the split needs LDAP or SAML sign-on in both tools, confirm the identity source is the same, because a user who exists in one directory and not the other will also produce mismatched assignments.

Running open-source asset tools alongside the rest of ServiceNow

Some organizations keep ServiceNow for incidents, changes and service catalog work, but move hardware and software asset records to GLPI or Snipe-IT. This only works if the asset tool becomes the system of record and ServiceNow receives the data it needs through a documented feed. Otherwise two inventories disagree within weeks, and nobody can say which laptop is assigned to whom.

Inventory feed direction: Decide whether GLPI Agent data flows into GLPI only, with ServiceNow reading a copy, or whether ServiceNow stays the master for configuration items. Write this down before any import.
Identity sync: Confirm whether user records come from the same directory for both tools, such as LDAP or Active Directory, so that assignee names match.
Reporting: Ask who builds the cross-tool reports, and whether they run from exports or from a database connection your team maintains.
Private Stack or cloud integrations: Confirm with ServiceNow whether your edition supports the connector or import method you plan to use, since integration options differ by deployment model.
Check-in and check-out: Laptops and licenses checked out in Snipe-IT must not be duplicated as ServiceNow asset records unless that duplication is intended.

Confirm the integration scope and the owner of each record type with ServiceNow and your own platform team before scheduling any change.

How to move asset records out of ServiceNow

This sequence moves hardware, software license and contract records out of ServiceNow into a system your own team operates. It ends with GLPI or Snipe-IT holding reconciled asset records, GLPI Agent keeping hardware data current, and the ServiceNow asset tables retired under a documented exit.

Export asset, license and contract tables
An administrator exports the hardware asset, software license, contract and assigned-user tables from ServiceNow as CSV, Excel, XML or JSON. Each list export is subject to default record limits, so confirm those limits in your instance and split larger tables into filtered batches. Attachments such as purchase invoices and signed contracts do not come along in list exports and need a separate extraction through the REST API. The output is a dated set of files with record counts checked against the live list views.
Clean and map fields to the target
Map each ServiceNow field to a GLPI asset type, a contract record or a Snipe-IT model and category. Standardize serial numbers, asset tags, model names, locations and status values, and remove duplicate records that built up over years of imports. Agree an owner for each field with the people who will maintain it after cutover. The output is a field mapping document and cleaned files that pass a dry-run review.
Choose the tool for each record type
Decide which records belong in GLPI and which belong in Snipe-IT. GLPI fits inventory, contracts and financial data alongside the service desk, while Snipe-IT fits check-in and check-out of laptops, licenses and accessories to people, plus component tracking such as RAM and hard drives. Write down whether asset records live in the service desk or in a separate tool, and why. The output is a decision record that the asset, finance and service desk teams have each signed.
Load records into the target system
Import the cleaned data into a test instance of GLPI, and into Snipe-IT if check-in and check-out is in scope, using the import methods that each version supports for your asset types. Confirm the import path for each record type before loading production data. Import users through LDAP sync or SAML from your directory instead of typing them in. The output is a test instance where a sample of records matches the ServiceNow source field by field.
Deploy GLPI Agent in parallel
Install GLPI Agent on Windows, macOS and Linux endpoints so hardware and software inventory reaches GLPI while ServiceNow remains the system of record. Confirm the inventory server address and deployment method with your endpoint management tooling, and agree with the asset team how long both sources run side by side. The agent also supports network discovery, which should be checked against your segmentation policy. The output is a list of endpoints reporting to GLPI and a list of devices not yet covered.
Reconcile hardware and license records
Compare GLPI inventory with the migrated ServiceNow records, matching on serial number, asset tag and hostname. For each mismatch, decide which source is correct, update the record and note the reason. Check software license counts against installed software and purchased entitlements, since agent-reported installs and contracted seats often differ. The output is a reconciliation report showing matched, corrected and unresolved assets, with a named owner for each open item.
Rebuild workflows and custom fields
ServiceNow approval workflows, business rules, custom fields and catalog items do not carry over as working logic, so define each one again in GLPI or Snipe-IT and test it. Document the approval path for purchases, reassignments and retirements, and confirm the notifications users expect. Plan this work before cutover, because it is manual effort that the export does not cover. The output is a list of rebuilt processes with test results for each one, approved by the asset owner.
Cut over and retire ServiceNow asset tables
Freeze asset edits in ServiceNow, run a final delta export, load it, and move the asset team to GLPI or Snipe-IT as the system of record. Redirect any integration that feeds ServiceNow asset data from procurement or endpoint tools before deactivating anything. Keep an archived export with checksums and access controls, then retire the asset tables according to your retention policy. The output is a dated cutover record and an archive that auditors can inspect.

What the cost of open-source asset management actually includes

The license line is zero for self-hosted GLPI and self-hosted Snipe-IT, since both are free software under GPL-3.0 and AGPL-3.0 respectively. What you pay for is everything around the software: the servers or cloud instances, the database, backups, the time to roll out GLPI Agent to laptops and servers, and the people who map your ServiceNow asset data into GLPI or Snipe-IT. Hosting and backups recur every month. Agent rollout, data mapping and initial configuration are mostly one-time, although agent packaging and deployment keep needing attention as the fleet changes. Ask any implementation partner to split its quote into these lines so you can see which costs are one-time and which recur.

Optional hosted plans change that split. The GLPI Network subscriptions page lists public cloud at 19 euros per user per month and private cloud at 21 euros per user per month with a 25-user minimum, and self-hosted subscriptions for support from 100 euros per month (Basic, up to 10 agents and 500 assets) to 4,500 euros per month (Enterprise). Snipe-IT's pricing page states its self-hosted software is free and that hosted plans start at $399.99 per year, adding email support, automated upgrades and server maintenance. Check whether these prices are current before you rely on them. Staff time is the cost most often left out. Ask who will own agent deployment, asset lifecycle rules, license reconciliation and monthly reporting after go-live, and how many hours per month that represents in your environment.

Before you request a quote, ask for a written scope with these items: server and database sizing, backup and restore tests, the GLPI Agent packaging and deployment plan, the data mapping for hardware, software and contracts, training for the asset team, and the handover of upgrade work. Ask whether a support retainer covers GLPI or Snipe-IT upgrades and how plugins are handled, since GLPI 11.0 suspends plugins after a new version is detected. Request the assumptions behind the estimate, such as the number of endpoints and the share of records that need manual cleanup. A quote without those assumptions is hard to compare with a hosted renewal.

Questions buyers ask before replacing ServiceNow ITAM

How much effort and time does moving ServiceNow asset records to GLPI take?

The effort depends mainly on how much asset data you hold, how clean it is, and how many integrations depend on it. The main drivers are the number of asset classes you track, the volume of hardware and software records, whether contracts and financial fields must move with them, and how many people must validate the results. Export limits in ServiceNow, the mapping of custom fields to GLPI item types, and the rebuild of any approval or reporting logic also add work. No duration figure is supplied for this migration, so ask any implementation partner for a timeline built from a written scope after they inspect a sample export from your instance. Plan a pilot on one site or one asset class before the full load.

Can our own team run a GLPI asset migration without outside help?

Many teams can do it in-house if they have someone comfortable with a Linux server, a web application stack, and database administration, and if the asset scope is modest. Outside help is more useful when you need data mapping across many sources, custom inventory fields, or validation against finance records. DeployOpen plans, implements, integrates and documents self-hosted platforms in your own infrastructure, and most engagements are fixed-scope with deliverables agreed in writing before work starts. Whichever route you pick, ask for a written list of what the migration covers and what remains your responsibility after go-live.

What skills and staff time does a self-hosted GLPI and Snipe-IT setup need?

You need people for four ongoing roles: server and web stack administration, GLPI application administration, endpoint agent deployment, and asset process ownership. The administration work covers the web server, PHP runtime, database backups and patching. Agent deployment requires access to endpoints through your software distribution tooling. Asset process ownership covers defining statuses, locations, and check-in and check-out rules. Snipe-IT adds a second application to run if you use it for laptops, licenses and accessories. Ask your team to confirm who will own each role before you choose the architecture, because that decision drives the recurring workload.

Which GLPI and Snipe-IT versions and PHP and database requirements apply?

The current GLPI release line is 12.0.0, published on October 7, 2026, and GLPI 11.0.11 was published on October 1, 2026. The GLPI README on the main branch lists PHP 8.3 or later and MariaDB 10.11 or later or MySQL 8.0 or later, while the installation docs list PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 for GLPI 11.0. Only MySQL and MariaDB are supported. Snipe-IT v8.8.0 was published on September 30, 2026, and 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. Confirm the exact requirements for the version you deploy in its documentation before you size the servers.

How does GLPI Agent differ from ServiceNow discovery?

GLPI Agent is installed on each device and reports hardware and software inventory to GLPI, so collection is agent-based. It also supports network discovery and inventory, package deployment and remote ESX inventory, and runs on Windows, macOS and Linux. It is the successor of FusionInventory Agent. ServiceNow discovery depends on its own collection components inside the ServiceNow platform, so the operating model differs. With agents, you must deploy and update them on every endpoint, and you must decide how devices outside your management tooling will be covered. Test coverage on a sample of machines before you retire the existing discovery feed.

How are upgrades and backups handled for GLPI and Snipe-IT?

The GLPI update procedure requires you to back up the database, the application files and the config directory, including the glpi.key and glpicrypt.key files. You then replace the application files and run php bin/console db:update. Since GLPI 11.0, plugins are suspended after a new version is detected and must be reactivated after major updates, so schedule time for plugin testing. Snipe-IT upgrades should follow its own documentation and be preceded by a database and file backup. Build upgrades into a staging copy first, and confirm with your team which backups are retained and how restores are tested.

What does the migration cost, and which parts recur after go-live?

The software licenses for GLPI and Snipe-IT are free under their open-source licenses, so your costs fall into infrastructure, implementation, optional support and staff time. One-time costs include discovery of your current data, mapping, migration runs, validation and training. Recurring costs include hosting, backups, upgrades, agent maintenance and internal ownership. Teclib' offers GLPI Network hosted plans and self-hosted subscriptions, and Snipe-IT offers hosted plans from $399.99 per year. Ask any vendor or partner for a quote that lists each component separately, with the one-time and recurring items distinguished.

How DeployOpen scopes and delivers asset module replacement

Asset replacement succeeds or fails on decisions made before any data moves: which records live where, who owns reconciliation, and how the system is backed up and documented. DeployOpen agrees a written scope and deliverables first, then builds, migrates and hands over the asset platform inside your own infrastructure.

Written scope before any work

Most engagements are fixed-scope, so the scope, deliverables and timeline are agreed in writing before work starts. For asset replacement, that document should name which asset classes move (hardware, software licenses, accessories), which systems feed inventory, and which records stay in the service desk. DeployOpen does not publish a price list, so the quote follows directly from that written scope. Ask for the list of deliverables and the acceptance criteria for each.

GLPI or Snipe-IT implementation

The platform is installed and configured in your cloud account, data center or air-gapped network, with the inventory path chosen for your estate. GLPI fits teams that want inventory, contracts and tickets in one tool, with GLPI Agent on endpoints. Snipe-IT fits teams that mainly need check-in and check-out of laptops, licenses and accessories. Confirm the web server, database and authentication setup with your security team before go-live.

Migration and reconciliation support

Migration is where asset data usually goes wrong. Duplicate serial numbers, licenses bound to retired machines and users who have left the company all need matching against a source of truth such as your procurement records and directory. DeployOpen supports the extraction, mapping and reconciliation work within the agreed scope. Ask how discrepancies are logged and who signs off the final reconciled count.

Hardening and access controls

An asset register holds personal and financial data, so access needs the same care as the service desk. Scope the hardening work to the platform: protected configuration keys, directory-backed login, role separation between asset administrators and approvers, and the update procedure. Confirm with your identity team which login method you will use before go-live, since that choice drives who can see and change ownership records.

Backup and documentation

Asset records are hard to rebuild by hand, so backup is part of delivery, not an afterthought. The deliverables should cover database and file backups, the configuration secrets needed to restore, a tested restore procedure, and runbooks for inventory agents and check-out workflows. Ask who holds the restore keys and how often a restore is tested in your environment.

Optional retainers for upgrades

After handover, the platform still needs patching, upgrades and support. Upgrades are where asset platforms drift, for example when a major release suspends plugins or changes requirements. An optional retainer covers ongoing support and upgrade work at a scope agreed in writing. Ask what is included in the retainer, how upgrades are tested before production, and how long support hours are reserved each month.

Open-source alternative to ServiceNow IT Asset Management