PSA Migration and GLPI Integration
A live, two-way GLPI integration for MSPs and IT teams running GLPI today — and an honest account of what moves across from every other PSA.
How Solidlio helps
Solidlio connects to GLPI’s REST API and keeps both systems in step for as long as you need. Tickets sync in both directions; assets, software, contacts and suppliers sync into Solidlio. You map each GLPI entity to a Solidlio organization, each GLPI ITIL category to a ticket queue, and set per entity type which system wins a conflict. When Solidlio holds everything you need, you disconnect. There is no cutover weekend because there is no cutover.
Capabilities
| Capability | What it does |
|---|---|
| Two-way ticket sync | Pulls GLPI tickets and follow-ups as tickets and comments; pushes subject, description, status and priority back |
| Asset import | Imports Computer, Monitor, NetworkEquipment, Printer, Phone and Peripheral records |
| Software and licences | Imports the GLPI software register and its licence sub-items |
| Contact provisioning | Imports GLPI users as people with a customer portal membership |
| Supplier import | Imports GLPI suppliers as vendors |
| Entity mapping | Maps each GLPI entity to a Solidlio organization, so one GLPI serves many tenants |
| Queue routing | Maps GLPI ITIL categories to Solidlio ticket queues, so imported tickets land where staff work |
| Per-entity source of truth | Sets, per entity type, whether GLPI or Solidlio wins a conflicting change |
| Preview before import | Samples live GLPI records for each enabled entity type before anything is written |
| Per-run error reporting | Records counts, duration and a per-record error list for every sync run |
Built for MSPs and their clients
One GLPI instance frequently serves several client organizations. Entity mapping is how that becomes a multi-tenant import rather than one undifferentiated pile.
| Organization | MSP | |
|---|---|---|
| Connecting GLPI | Connects its own instance | Connects on the client’s behalf |
| Entity mapping | Maps into its own organization | Maps each GLPI entity to the right client organization |
| Queue routing | Routes to its own queues | Routes client tickets into the queues its technicians already work |
| Scope of the mapping | — | Restricted to organizations the MSP owns or manages; others are rejected |
How it works
- Connect — enter your GLPI URL, app token and user token. Solidlio tests the credentials live and reads back your GLPI version. HTTPS is required; plaintext connections are refused because the tokens travel on every call.
- Preview — Solidlio samples live records for each entity type you enabled, so you confirm you are pointed at the right instance before anything is written.
- Map — GLPI entities to organizations, locations to locations, ITIL categories to ticket queues. Fields whose names differ get an explicit pair.
- Choose what syncs — per entity type: on or off, how often, and whether GLPI or Solidlio is authoritative.
- Run a full sync — it queues and returns immediately with a run id. Sync History shows counts, duration and any per-record errors as it goes.
- Run continuously, then leave — scheduled syncs keep both sides current for as long as you want. Disconnect when Solidlio holds what you need.
What ships, and what does not
Stated plainly, because a migration plan built on a roadmap is a failed migration.
| System | Status |
|---|---|
| GLPI | Ships — two-way tickets, inbound assets, software, contacts, suppliers |
| QuickBooks Online | Ships — customer import, provisions managed-client tenants |
| Assets and products from any system | CSV import |
| ConnectWise Manage, Autotask, Halo PSA | Roadmap. No integration exists; setup is refused server-side |
Tickets, companies, contracts and time entries from a non-GLPI PSA have no import path. The REST API is the supported route, and Enterprise onboarding includes migration assistance.
Limits worth knowing before you plan
- Ticket write-back pushes four fields — subject, description, status, priority. Comments, assignees and time entries stay in Solidlio.
- Write-back runs on the full-sync cadence, not in near-real time, and requires tickets to be set to
solidlioas source of truth. - Assets, software, contacts and suppliers are inbound only.
- Software always takes GLPI as authoritative, whatever the source-of-truth setting says.
- No network, IP or port data syncs. GLPI ticket tasks are not synced; follow-ups are, as comments.
Security
- GLPI credentials are encrypted at rest and never displayed again.
- HTTPS is required at connect; plaintext URLs are refused.
- Outbound requests to your GLPI instance pass an SSRF guard that re-validates the resolved address at connection time, so a hostname cannot be re-pointed at an internal address between the check and the request.
- Entity and queue mappings are restricted to organizations and queues your account owns or manages.
- Every route requires organization administrator or above.
Plans and access
Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.