ManageEngine implementation
in Poland: stages, costs, and mistakes

A practical guide for IT managers: what a ServiceDesk Plus implementation looks like, how long it takes, how much it costs, and what to avoid.

Back to blog
ITSM - ManageEngine
Jakub Roszkiewicz May 2026 13 min read

ManageEngine implementation in Poland is not just license purchase and install. It is the process that decides whether in six months the help desk will be actually used, or become an expensive toy in the IT catalog. From our experience: more than half of companies that tried to deploy ServiceDesk Plus on their own got stuck at the SLA and ticket category configuration stage. This article shows how to avoid that.

How an implementation differs from buying a ManageEngine license

Buying a ManageEngine ServiceDesk Plus license is a transaction: you pay Zoho Corporation for the right to use the software. You get a license key, an installer file, and access to the documentation. That is all.

An implementation is something completely different. It is the process of fitting a finished product to your organization: department structure, SLA policy, change management processes, integrations with Active Directory, ERP, or monitoring systems. Without implementation you end up with an empty instance using English templates, generic ticket categories, and zero integration with the rest of the infrastructure.

A practical difference: a Standard license for 10 technicians is an expense the company feels immediately. Lack of implementation hits you only after three months, when it turns out that technicians still use Excel and the IT manager has no reports to present to the board.

Practical note: Zoho does not require the customer to implement through a partner. You can buy a license directly and deploy on your own. The only question is whether you have someone on the team with three years of ITIL experience, knowing the ManageEngine REST API and having time for a 6-8 week project.

Free consultation

ITSM implementation for your company - start with a needs analysis.

No-obligation needs analysis - 30 minutes online.

Book 30 min

ManageEngine implementation stages: from analysis to production

Every ManageEngine implementation we run goes through six stages. Skip any of them and problems appear in the third or fourth month after go-live.

1. Pre-implementation analysis (1-2 weeks)

  • Mapping IT processes: how tickets currently look, who receives them, how they are escalated
  • Identifying stakeholders: IT manager, technicians, HR (onboarding), controlling (reports)
  • Audit of current infrastructure: Active Directory, mail server, monitoring, ERP
  • Defining measurable goals: 30% MTTR reduction, 4h SLA for P1, monthly reports

2. Technical design (1 week)

  • Version selection: Standard, Professional, or Enterprise (differences in CMDB, Change Management, Project Management)
  • Decision: On-Premise (customer-hosted server) or Cloud (Zoho instance)
  • Server sizing: 8 GB RAM for 5,000 tickets per month, MS SQL or PostgreSQL
  • Integration plan: AD/LDAP, email, monitoring (e.g., PRTG, Zabbix), ERP

3. Installation and base configuration (1-2 weeks)

  • Server installation, database, SSL certificate, backup
  • Translating the interface and templates into Polish
  • Configuring departments, support groups, roles, and permissions
  • Active Directory integration: user sync, SSO

4. ITSM process configuration (2-3 weeks)

  • Incident Management: categories, priorities (Impact x Urgency matrix), automatic assignments
  • Service Catalog: IT service catalog with request forms (new employee, system access, hardware purchase)
  • SLA: business clocks, escalations, notifications
  • Change Management: approval workflow, CAB
  • CMDB: asset import, relationships between CIs

5. Testing and training (1-2 weeks)

  • UAT with the IT team: test scenarios, workflow corrections
  • Training technicians (8h) and managers (4h)
  • Self-service portal training for end users (1h, online)
  • User documentation in Polish

6. Go-live and hypercare (2-4 weeks)

  • Ticket migration from the previous system (if any)
  • Production start with active on-site consultant support
  • Daily reviews in the first week, weekly afterwards
  • Workflow corrections based on real tickets

How long a ManageEngine ServiceDesk Plus implementation takes

Implementation time depends on three variables: company size, number of integrations, scope of ITIL processes. Concrete timeframes from our projects:

Implementation typeCompany profileDelivery time
Quick Win30-80 employees, single IT department, Incident + Self-Service4-6 weeks
Standard implementation80-250 employees, Incident + Service Catalog + SLA + AD/Email6-10 weeks
Full ITIL200-500 employees, plus Change + Problem + CMDB10-16 weeks
Enterprise with integrations500+ employees, ERP / monitoring / HR / custom REST API integrations16-24 weeks

The most common delays in Polish projects do not come from technology. They come from decision-maker availability on the client side. A three-week delay in approving the priority matrix is a classic. That is why every project starts with a schedule that already has decision-meeting dates booked.

Cost of ManageEngine implementation in Poland: what is included

The cost of a ManageEngine implementation in Poland has to be broken into three components, because combining them into one number misleads the customer.

Component 1: ManageEngine licenses

License pricing is the Zoho Corporation - customer relationship. It depends on the edition (Standard / Professional / Enterprise), the number of technicians (not end users), and the billing period (1 / 2 / 3 years, with discounts for longer commitments). For a 100-250 employee company with 5-10 technicians, the Professional edition runs into low five figures in PLN per year. The Enterprise edition with CMDB and Change Management runs into tens of thousands. Detailed price ranges for 5-500 technicians are in the article ManageEngine ServiceDesk Plus price and licenses.

Component 2: Implementation (consultant services)

This is the work of a certified implementer: analysis, configuration, integrations, training. The quote depends on the number of consultant-days. A standard implementation for a 100-250 employee company is a budget ranging from low to mid five-figure PLN net, depending on integration scope and ITIL process depth.

Component 3: Post-implementation support

This is where customers most often try to save and later regret it. Support includes: technical assistance, workflow corrections, small integrations, training new technicians, assistance with updates. Billed in hour packages (e.g., 20h/month) or as an SLA subscription.

Pricing trap: The cheapest ManageEngine implementation offers on the Polish market rely on minimal scope (3-5 consultant-days). That is enough for installation and interface translation. It is not enough to design a sensible Service Catalog or AD integration in an environment with GPO policies. Ask directly: how many consultant-days are in the quote, and what exactly do they cover.

The most common mistakes in self-implementing ManageEngine

1. "Quick and dirty" configuration without process analysis

A classic: someone in IT installs ServiceDesk Plus, enables the default categories, and announces the launch. After a month it turns out that 60% of tickets land in the "Other" category because real processes were never mapped.

2. SLA without business clocks

By default SLA counts 24/7. A Friday 17:00 ticket with an "8h resolution" SLA is breached by Saturday morning, even if the help desk works 8-16. Configuring Business Hours requires setting up a holiday calendar, working hours, and exceptions per team.

3. No Active Directory integration

Manual user creation in SDP while AD already has all the data. After half a year the SDP database has 200 users while AD has 350, and nobody knows which ones are active.

4. Service Catalog copied from Zoho documentation

Zoho provides sample templates in English. The implementation ends by enabling them without translation and without adjusting to the company's real services. End users do not understand the forms and go back to phone calls.

5. No maintenance process

Implementation done, consultant gone, system running. After six months: new departments, new services, SLA changes, and nobody updates it. The system stops matching reality.

How to choose a ManageEngine implementation partner in Poland

The ManageEngine Poland partner market is narrower than it looks. The number of firms that actually implement (and not just resell licenses) is in the low double digits. Four things are worth checking.

ManageEngine certifications

ManageEngine runs a certification program for implementers. Ask about named certifications for the consultants who will run your project, not about the firm's partner status. Partner status speaks to sales; a named certification speaks to implementation competence. Before choosing a deployment model, also check the OnPremise vs Cloud comparison. That decision affects implementer workload.

Number of real implementations in Poland

Ask for references from the last 24 months. Best from an industry close to yours (manufacturing, finance, retail, MSP). A ManageEngine implementation in a 200-person manufacturing company has a different dynamic than in a 30-person software house.

Post-implementation support

What does the partner offer 6, 12, and 24 months after go-live? Is there a response SLA? Are consultants available at upgrade time, or do you have to negotiate a new project every time? Lack of real post-implementation support means that in a year you are left alone with a system that requires specialized knowledge.

Integration experience

ManageEngine has a REST API, but integration with Polish ERPs (Comarch, enova365, Symfonia) or industry systems requires experience. Ask about specific integrations the partner has delivered, ideally with technical documentation.

Case study: ManageEngine implementation for a 200-employee manufacturing company

Manufacturing companies have specific help desk requirements - they must serve both IT infrastructure and OT devices on the shop floor. We describe this in detail in our guide to implementing an IT help desk in a factory, including how to configure SLAs for production lines.

Illustrative scenario - Manufacturing

Starting situation

The description below is an illustrative, realistic implementation scenario based on typical projects - numbers are for illustration only. A metalworking manufacturer, 200 employees, two plants, an IT department of 6 (3 technicians, 1 administrator, 1 OT specialist, 1 manager). Tickets handled via a shared mailbox and Excel. No SLA, no board reports, average response time unknown.

Implementation goals

Introduce ServiceDesk Plus Professional, integrate with AD and Office 365, build a Service Catalog for 8 service categories, configure SLAs with 6:00-22:00 business clocks (two production shifts), build a CMDB with 280 IT assets and 50 OT assets, set up monthly reports for the board.

Course of work

Analysis: 2 weeks. On-Premise installation on the customer's server with MS SQL: 1 week. Process configuration: 3 weeks (including Service Catalog, categories, and SLA policy configuration). CMDB and asset import (Discovery Agent for IT, CSV import for OT): 1 week. Training and UAT: 1 week. Go-live with hypercare: 2 weeks. Total: 10 weeks.

Expected outcomes

Typical expected outcomes in this kind of implementation include: introducing measurable response time on P1 tickets (previously not measured at all), ongoing SLA compliance reporting, a significant reduction in the share of tickets falling into the "Other" category thanks to a properly designed category tree, an automatic monthly report for the board, and a part of tickets being handled through the self-service portal. Concrete values depend on process discipline and team engagement - they are worth defining as measurable implementation goals.

How to start: a free consultation with Rotech Group

We are certified ManageEngine implementers, not resellers. We specialize in implementations for companies of 50-500 employees in Poland. Every implementation starts with a free consultation in which we:

  • Map current IT processes and identify optimization areas
  • Pick the right ManageEngine edition (Standard / Professional / Enterprise)
  • Present an initial schedule and scope of work
  • Indicate risks and areas that require special attention

The consultation takes about 60 minutes and runs online or on the customer's premises. No obligations and no salesperson on the line.

Sources and further reading
JR
CTO - ITSM & ManageEngine Expert - Rotech Group
ManageEngine implementation with Rotech Group

Plan your implementation with certified implementers

A free consultation covers IT process analysis, ManageEngine edition selection, and an initial schedule. No obligations.

Book a free consultation
Book a free consultation