Insights
Moving from Freshservice, ManageEngine or spreadsheets to GLPI: a practical guide
10 November 2026 · Distillect
Most South African IT teams do not want a migration project. They want fewer tools, a trustworthy laptop register, and a helpdesk bill that does not jump with every hire.
This guide covers a move to hosted GLPI with Distillect (a registered Teclib partner) from Freshservice, ManageEngine, or a shared inbox plus spreadsheets: what migrates, what does not, timeline, risks, and the free trial path.
Still comparing cost and data location first? See helpdesk software for South African IT teams and the GLPI hosting page.
Start with the problem, not the feature grid
A migration fails when the brief is “copy every ticket forever.” It succeeds when the brief is: open work must not get lost, people and groups must recognise the portal, categories and SLAs must feel familiar, and the asset register must become trustworthy.
Ask four questions before you export anything:
- What must work on Monday after cutover (open tickets, VIP queues, password resets)?
- What can stay archived in the old system for reference?
- Is the asset register a source of truth, or a spreadsheet that has drifted?
- Who owns categories, SLAs and the knowledge base after go-live?
Distillect’s free migration assessment is where those answers get honest. If GLPI is not the fit, that is a valid outcome.
What usually migrates
GLPI is open-source ITSM: incidents, requests, problems, changes, inventory, a CMDB and asset financials in one system. Distillect hosts it in South Africa and invoices hosting and support in rand.
Tickets (current open work). Open incidents and requests with comments or condensed history; priority, status, assignee/group, category and requester mapped into GLPI; attachments where practical. Skip multi-year ticket archaeology — keep the old tool read-only if auditors need history.
Users and groups. Technician and end-user accounts, or a directory sync plan (LDAP / Entra ID); groups or queues that match how work is assigned today; roles for self-service versus technician views.
Categories, catalogue shape and SLAs. Incident and request categories your team already uses; a first pass at a service catalogue if you have one; response and resolution targets by priority (or category); business hours on a South African calendar. Distillect support itself runs during SA business hours.
Knowledge base. Articles that are still accurate — retire the rest rather than importing noise.
Assets, CMDB and financials. Hardware records (type, serial/asset tag, assignment, warranty or purchase date where you have them); software licences where the register is trustworthy; a CMDB starter set of configuration items that tickets actually reference — not a twelve-month data programme as the entry ticket. Purchase value, warranty and refresh dates can sit with the asset so finance is not an export archaeology project later.
What usually should not migrate on day one
- Every closed ticket for all time (archive; do not drown the new queue)
- Broken or duplicate asset rows (cleanse in the trial first)
- Custom automations nobody can explain (recreate only what still matters)
- Pixel-perfect clones of another vendor’s portal
- Every integration on week one (email-to-ticket and directory sync first)
- Unresolved political workflows (GLPI will not invent a CAB you do not run)
Realistic timeline
Typical for a 5–25 agent South African IT desk. Not a contractual SLA.
Week 0 — Assessment (free). Current tool, agent count, ticket volume, must-have workflows; sample exports or screenshots of categories, SLAs and asset columns; decide trial, migrate, or stop.
Weeks 1–2 — Pilot on a hosted trial. Distillect provisions a 30-day hosted trial; map users, groups and categories; import a slice of open tickets and a clean asset sample; technicians work real scenarios. You can also click the public live demo on the GLPI page first (technician and self-service guest accounts).
Weeks 3–4 — Harden and train. Finalise SLA rules, email ingestion and branding; short role-based sessions for agents and a champion in each business unit; agree cutover weekend and rollback (old system read-only, not deleted).
Cutover weekend. Final open-ticket sync; email/MX cutover if the mailbox changes; smoke tests — create as end user, assign as tech, link an asset, hit an SLA timer.
First 30 days in production. Email support during SA business hours under Hosted Starter or Growth; weekly triage of category misuse and missing fields; freeze non-essential integrations until the queue is calm.
Larger estates take longer; the assessment is where that shows.
Risks — and how Distillect handles them
| Risk | What it looks like | How we handle it |
|---|---|---|
| Lost open work | Ticket closed in old tool, invisible in new | Controlled open-ticket import plus a short dual-run; never a big-bang history dump |
| Dirty assets | Two laptops, one serial, three owners | Cleanse sample in the trial; production import only after rules are agreed |
| Agent rejection | “The old portal was nicer” | Train on their queues; keep branding familiar |
| Email black hole | Replies still hitting the old mailbox | Document MX/forwarding; test before cutover Friday |
| Scope creep | “While we’re at it, rebuild HR services” | ITSM first; other departments after the desk is stable |
| Wrong product fit | Enterprise platform needs vs helpdesk needs | Say no on the assessment if you need a multi-year platform programme (ServiceNow framing) |
Distillect does not claim a named data-centre brand or certification badge on the marketing pages. Hosted instances are hosted in South Africa; the service is designed to support POPIA compliance. Location, access and retention belong in the assessment or security questionnaire.
The 30-day trial path
- Tell Distillect about the desk — name, team size, current tool, what hurts. Form on distillect.co.za/glpi.
- Hosted trial — once it is a fit, you get a hosted GLPI instance for your own scenarios. No per-agent clock, because there isn’t one.
- Decide — keep the instance on Hosted Starter (up to 10 agents: R3,500/month excl. VAT + R18,000 setup) or Hosted Growth (up to 25 agents: R7,500/month + R28,000 setup), book a deeper migration, or walk away. Free and without obligation.
Packages are capped by agent count to size hosting and support — not because GLPI bills a seat licence.
From each starting point
Freshservice. Easy to like; usual triggers to leave are the USD per-agent bill, data location, or needing assets and CMDB with the ticket rather than beside it. You need current open work, people and groups, categories, and an asset plan — not every historical ticket. Commercial comparison: Freshservice alternative.
ManageEngine. Often sold as bundled modules. List which modules you actually use day to day, and which were shelfware, so you do not rebuild unused complexity. GLPI keeps helpdesk, assets, CMDB and financials in one open-source codebase.
Spreadsheets and a shared inbox. Often the cleanest migration: little to export, much to design (categories, first asset register, a portal instead of it-support@…). Budget training time so technicians stop living in Outlook.
When not to migrate yet
- Mid-contract with punitive exit fees and no budget pain — wait for renewal, but run the trial so the decision is informed.
- Leadership wants company-wide ESM in one leap — that is a different project.
- Nobody will own the asset register after go-live — fix ownership first.
Next step
Book a free migration assessment or start a free 30-day hosted trial at distillect.co.za/glpi. Bring a screenshot of your categories, your agent count, and one sentence on what hurts. That is enough to start.
Distillect — registered Teclib/GLPI partner. Data hosted in South Africa. Invoiced in rand. Support during SA business hours.
Hosted GLPI, hosted in South Africa.
No per-agent licence fees. Flat rand packages. Free 30-day trial or a free migration assessment.