You do not have to replace Pohoda to get a CRM. The CRM is built next to it and shares data with it through the XML interface, or through POHODA mServer. Pohoda handles business contacts, quotes and orders, but its pages do not mention deal stages, an activity plan or an overview for a sales manager. A CRM covers those. At Lumenax the price for a firm of 6 to 20 people with only a CRM module comes to CZK 260,000 to 610,000 according to its calculator.
- You do not have to replace Pohoda; the CRM is built next to it.
- The word REST is not on Stormware's API page; it describes XML and mServer.
- mServer answers requests, so the CRM has to keep asking Pohoda.
- Access through Odoo's external API is only in Custom plans.
- CRM only for 6 to 20 people: CZK 260,000 to 610,000 per the Lumenax calculator.
The Pohoda figures are from Stormware's pages as of 25 October 2026, the Lumenax figures from lumenax.cz on the same day.
What Pohoda does in sales and what it does not
According to Stormware, Pohoda has an address book in all variants: management of business contacts, communication functions, document organisation and GDPR. It adds quotes, enquiries and orders from the Lite variant up. Customers are therefore there, with their documents.
What Stormware's pages do not mention are deal stages, expected value and the chance of a closed deal, an activity plan and reminders. Those are things a salesperson needs every week. If you keep them in a spreadsheet and in e-mails, you have two truths, and the person who leaves first keeps one of them.
You are not alone. According to the Czech Statistical Office, only 30.0% of firms with 10 to 49 employees use a CRM, 57.2% of firms with 50 to 249 employees, 70.0% of firms with 250 or more employees, and 36.2% of all firms with 10 or more employees (2025).
Three ways to add a CRM to Pohoda
| Way | What it means | Where it hurts |
|---|---|---|
| A CRM with no link | Sales works in one program, the accountant in another | Invoices never reach the CRM, quotes are retyped into Pohoda by hand |
| Exchange of files | Export and import of documents, for example in XML or CSV format | The data is always one export old and someone has to run it |
| A link through the XML interface or mServer | The CRM asks Pohoda by itself and sends documents into it | Pohoda must be running, and the design takes work and tests |
Which one suits you depends on how many documents arrive a day and who has to do what with Pohoda. In our judgement the first or second is enough for one salesperson. With more people entering quotes, the cost of manual reconciliation grows.
How to talk to Pohoda: XML and mServer
If you are looking for a "Pohoda REST API", the word REST does not appear on the Stormware page. Stormware describes the XML interface, through which "practically any data" can be exchanged with Pohoda, and which also handles CSV and PDF. Among its examples it lists warehouse and till systems and e-shops.
One route is POHODA mServer. It is an HTTP server that carries XML in a request and response pair: the client asks, mServer answers. It follows that the CRM has to keep asking Pohoda. The page describes no other way in which Pohoda would report changes itself.
mServer is part of the Pohoda program, so Pohoda must be running, and one of its instances is reserved only for exchanging data. Stormware recommends running it on a server system, on an internal network and not on a computer with a public IP address. Among its suggested uses it also lists a link over a VPN. Stormware also writes that the automatic launch of XML exchange from the program is only in the E1 line. The page does not say which line supports mServer; check with Stormware before you start the project.
Odoo CRM: what to expect
Lumenax builds its CRM on open source Odoo 19. According to odoo.com, deals are managed by dragging between stages, quotes can be sent in a few clicks and the handling of cases can be partly automated. Lumenax describes its CRM as a kanban with expected value and probability, quotes from the warehouse and price lists, activities with reminders and a customer history with orders and invoices on one card.
On the Odoo side, version 19 has an external JSON-2 interface over HTTP with a key in the header. Odoo's documentation states that access to data through the external API is only in Custom plans, not in Standard or One App Free. According to the Czech price list, Odoo Online on the Custom plan costs EUR 33.90 per user per month, or EUR 27.90 with annual payment. The cheaper Standard plan is Odoo Online without customisation and has no external API. According to Odoo's guide an API key lasts at most three months, so you will be renewing keys.
Lumenax runs its own server, where the Odoo licence costs CZK 0. It offers a link to other systems, Pohoda among them, as custom work and prices it after the fit-gap analysis. It does not mention a ready-made Pohoda connector on its pages.
What it costs
Running at Lumenax costs CZK 3,400 a month for the server and CZK 249 per full user, that is CZK 4,645 a month for 5 users and CZK 7,135 for 15. The one-off project is estimated by the calculator, with the option "We are extending an existing system", as follows:
| Scope | Project estimate |
|---|---|
| CRM only, 1 to 5 people | CZK 190,000 to 450,000 |
| CRM only, 6 to 20 people (6 to 15 users) | CZK 260,000 to 610,000 |
| CRM and warehouse, 6 to 20 people | CZK 290,000 to 680,000 |
The estimates assume a basic data transfer and a standard link to surrounding systems. The calculator states that a link to other systems adds CZK 25,000 to 120,000 depending on complexity. Cleaning faulty data is not included. You get a fixed price after the fit-gap analysis, an hour of work outside the fixed price costs CZK 3,300, or from CZK 2,200 for larger volumes. Lumenax gives the length on its ERP page as 4 to 12 weeks; for a small project with a CRM and accounting for 5 users the calculator says 6 to 10 weeks. A breakdown of prices is in the article on the cost of Odoo.
How to build it so the data does not fight
These are tips from practice, not quotes from the vendor.
- One source of truth for each kind of data. Pohoda owns documents and accounting, the CRM owns the relationship with the customer: notes, activities and deal stages. For data that overlaps, such as addresses, decide in advance which system wins.
- Test on a copy. Before the CRM touches live Pohoda data, try the link on a copy of the database.
- What hurts first. Start with a quote from the CRM creating a document in Pohoda. Add the rest after a month of operation.
- Agree who looks after keys and passwords. Access to mServer and an API key is access to company data.
If you are only now leaving spreadsheets for sales, go through the five signs from the article on Excel and ERP. If you are unsure whether to take a CRM or go straight to an ERP, read the comparison of Pohoda, Money S3 and Helios. Free CRMs are covered in the article on free CRM.
Common questions
Do we have to replace Pohoda?
No. Pohoda stays as the accounting system and the CRM runs next to it. The accountant's procedure does not change; only a sales layer is added.
Does Pohoda have a REST API?
Stormware's site describes an XML interface and POHODA mServer, an HTTP server carrying XML. The word REST is not there.
Which version of Pohoda connects to a CRM?
Stormware's page on the XML interface does not distinguish variants, so you cannot tell from the site whether XML or mServer is limited to a line. The automatic launch of XML exchange from the program is only in the E1 line. Check with Stormware.
Which CRM does Lumenax use?
The CRM in xOffice, built on open source Odoo 19. The licence costs CZK 0, running costs CZK 3,400 a month plus CZK 249 per full user. The system runs on Lumenax's server in the EU or on your own.
What if our Pohoda is heavily customised?
Custom agendas and user fields are only in the E1 line. Customisations affect the scope of the link to surrounding systems, so go through them during the fit-gap analysis. The calculator does not account for them; it counts a basic or standard link.
Sources
- Stormware, POHODA: XML API communication, viewed 25 October 2026: https://www.stormware.cz/pohoda/xml/
- Stormware, POHODA mServer (updated 16 June 2023), viewed 25 October 2026: https://www.stormware.cz/pohoda/xml/mserver/
- Stormware, POHODA: Comparison of variants, viewed 25 October 2026: https://www.stormware.cz/pohoda/varianty/
- Odoo 19.0 documentation, External JSON-2 API, viewed 25 October 2026: https://www.odoo.com/documentation/19.0/developer/reference/external_api.html
- Odoo, CRM, viewed 25 October 2026: https://www.odoo.com/app/crm
- Odoo, pricing, viewed 25 October 2026: https://www.odoo.com/pricing
- Lumenax, CRM system, viewed 25 October 2026: https://www.lumenax.cz/crm-system
- Lumenax, xOffice ERP system, viewed 25 October 2026: https://www.lumenax.cz/erp-system
- Lumenax, calculator (constants in the page script and common questions), viewed 25 October 2026: https://www.lumenax.cz/kalkulacka-erp
- Czech Statistical Office, ICT in enterprises, data for 2025, viewed 25 October 2026: https://csu.gov.cz/ict-v-podnicich
How to choose an ERP system: 7 questions before you sign
Free CRM: when it's enough and when it costs more than a paid one
Migrating from ABRA: What the Process Actually Looks Like
