Comarch Optima is one of the most popular ERP / finance and accounting solutions for Polish SMBs. Optima is positioned below Comarch ERP XL: it is simpler and cheaper, but its API is more limited. The question is whether it is worth integrating Optima with ManageEngine ServiceDesk Plus. The answer is yes, but in a different way than with SAP or XL. This article shows how Optima integration works, how long it takes to roll out, and when it is worth considering an upgrade to XL instead of integrating Optima.
Optima ERP: what it is and how it differs from XL
Optima is the SMB-scaled edition from Comarch. It covers: accounting, warehouse management, sales, and purchasing. It does not cover: multi-entity, advanced workflows, or system integrations (beyond a basic REST API).
When is Optima enough: SMB-segment companies, single-site, without complex system integrations. Optima is cheaper to license than Comarch ERP XL; current prices for both products should be verified with a Comarch partner.
When to upgrade to XL: more than 300 employees, multiple sites, advanced reporting, system integrations (HR, manufacturing, finance). Rotech Group view: if you are planning to grow, start with XL, because an Optima to XL migration is painful.
Optima + ManageEngine integration: what it synchronizes
Users
- Import from Optima: ID, first name, last name, email
- Org structure: department, manager, cost center
- Synchronization: every 4 hours in batch
- Benefit: helpdesk always has an up-to-date list
Cost centers
- Import: CC code, name, budget
- Mapping: employee to CC, ticket to CC
- Reporting: IT cost per CC per month
- Benefit: accurate cost audit for controlling
Assets
- Import: inventory number, type, value, acquisition date
- Linkage: asset to employee, asset to CC
- Tracking: amortization, warranty, depreciation
- Benefit: single source of truth for inventory
New hires
- HR creates the record in Optima, then an auto ticket appears in ManageEngine
- Ticket: "New Employee Onboarding"
- SLA: 2 days to IT readiness
- Benefit: zero forgotten accounts
5-day rollout: what happens
- Day 1: Optima data audit, API access, documentation
- Days 2-3: Field mapping (users, cost centers, assets), synchronization prototype
- Day 4: Testing on sample data, mapping validation
- Day 5: Go-live, full data sync, monitoring
Comparison: Optima vs XL vs SAP for ITSM
| Criteria | Optima | Comarch XL | SAP S/4HANA |
|---|---|---|---|
| REST API | Limited | Advanced | Full OData |
| Rollout time | 5 days | 7-10 days | 4-8 weeks |
| Integration complexity and cost | Lowest | Medium | Highest |
| Volumes | <200 users, <500 assets | 200-500 users, <2000 assets | 1000+ users, 10k+ assets |
| Real-time webhooks | No (batch every 4h) | Optional | Yes |
| Multi-entity | No | Yes (limited) | Yes (full) |
Conclusion: Optima works for SMBs of around 100-200 people. XL is for growing companies. SAP is for enterprise. If you are on Optima and planning to grow, plan an upgrade in years 2-3, because the migration is expensive.
Optima limitations: what will not work
- No webhooks: synchronization is batch only every 4 hours, up to a 4-hour delay is possible
- No multi-entity: with more than one branch, Optima does not scale the data
- Limited custom fields: you cannot add your own fields to the Optima API
- No asset auto-discovery: assets have to be imported manually, no SNMP/WMI
- Rate limiting: the Optima API is slower than XL; with more than 1000 assets sync can be slow
Scenario: a wholesale company of ~80 people on Optima
Illustrative scenario (not a description of a specific client): a wholesale company employing about 80 people, using Comarch Optima, with no ITSM system in place. Typical problems: who has access to which systems? Which equipment is assigned to which employee? How much does IT support cost for each department?
Solution: Optima + ManageEngine ServiceDesk Plus integration. User, cost center and asset synchronization in batch mode.
Result: ERP data is available in the helpdesk. Technicians see which employee they are serving, which department and which cost center. It becomes possible to report IT support costs broken down by department, which was previously impossible to measure.
Benefits: time saved on manual data reconciliation, better control of IT costs, and order in access management (it is clear who has access to what). The size of the benefits depends on company size and the quality of the ERP data.
FAQ
When is Optima enough and when should you upgrade to XL?
Optima fits companies with 50 to 300 employees, single-site, without advanced integrations. Upgrade to XL when: more than 300 people, multiple sites, complex workflows, system integrations. If you are planning to grow, plan the upgrade for year 2-3.
What is the difference between Optima and XL for ITSM?
Optima: limited REST API, modest documentation, 5-day rollout. XL: advanced REST API, good documentation, multi-entity, 7-10 day rollout. Both are from Comarch, but XL has more features. For SMBs: Optima is fine.
Can you start with Optima and later upgrade to XL?
Not without a resync. The Optima schema differs from XL. An upgrade requires mapping revalidation and a full resync. Rotech Group view: if XL is where you are heading, start with XL rather than Optima.
How long does the rollout take?
5 days: day 1 API analysis, days 2-3 mapping, day 4 testing, day 5 go-live. It may be longer with legacy data, custom fields, or more than 1000 assets. For a standard SMB, 5 days is realistic.
Real time or batch?
Optima: batch every 4 hours (standard); webhooks are difficult. For SMBs batch is enough, a 4-hour delay is acceptable for a helpdesk.
Related articles
ManageEngine + Comarch ERP integration in Poland ManageEngine + SAP S/4HANA: enterprise integration API integrations: a full guideDoes Optima integration make sense for your company?
Rotech Group will run an audit: is Optima enough, or do you need an upgrade to XL. A rollout plan with no surprises.
Book a consultation →