Five industries worked hands on, so we arrive knowing where the gaps usually are.
All industries →Request a demoFour ERP platforms in house, and fifteen capability modules. The recommendation is never tied to a licence quota.
All solutions →Request a demoOne team from platform selection through to the reports on your desk.
All services →Request a demoGuides, how-tos, comparisons and a plain-English glossary, written by the consultants who deliver the projects. No form in front of any of it.
Nobody in UAE ERP publishes their tools or their pricing. We do both.
Free tools →Request a demoAn ERP and IT consultancy in Business Bay, Dubai, implementing Oracle, Microsoft, Odoo and SAP across the UAE and GCC.
Consultants in the UAE, technical team in South Asia. Cost stays sharp without cutting corners.
About QZ Infomatics →Request a demoKeep the system working after go-live —
or take over one that stopped working a while ago.
QZ Infomatics provides ERP support services, annual maintenance contracts, role-based user training and system migration for UAE businesses — on systems we implemented and on systems another vendor built. A support contract covers user assistance, bug fixes, report and form changes, minor enhancements, version upgrades and health monitoring, with response times set by severity rather than by whoever shouted last. Taking over an existing deployment starts with a system audit, which is what makes the support price a number rather than a guess.
After go-live
Most ERP problems in the UAE are not implementation problems. They are what happened in the eighteen months afterwards. None of it shows up on day one; it shows up at year-end, when the auditor asks a question the system can no longer answer.
QZ Infomatics provides ongoing ERP support services, structured user training and migration work for UAE businesses — on systems we implemented, and on systems we did not.
Three things
Bought together more often than separately, because they are the same problem showing up at different moments in a system's life.
Day-to-day support under an annual maintenance contract: user questions, bug fixes, configuration changes, new reports, minor enhancements, module additions and version upgrades. Response times are set by severity in the contract, so a payroll-blocking issue and a report tweak are not treated the same way.
Role-based training built around what each person actually does in the system, rather than a single walkthrough of every menu. Delivered on your own data, with recorded sessions and written procedures, so new joiners are not dependent on someone remembering how it was set up.
Moving to a new platform, a new version, or off a legacy system. The discipline is the same every time: audit what exists, define what moves, cleanse it, load into test, reconcile, then repeat for the live cut-over.
Still building rather than running? ERP implementation → ERP consulting →
The line in the contract
Where that line sits is agreed in writing before the contract starts. Disputes about whether something is “support” or “a project” are the most common source of friction in ERP support relationships, and they are entirely avoidable.
| Included | Quoted separately |
|---|---|
| User support and issue resolution | New modules and new entities |
| Bug fixes and configuration corrections | Workflow redesign |
| Report, form and dashboard changes | Custom development and integrations |
| Minor enhancements within existing modules | Major data migration projects |
| Version upgrades and regression testing | On-site training beyond the annual allowance |
| System health and performance monitoring | Third-party licence costs |
| Annual allowance of refresher training days | — |
Pricing follows the same logic. An AMC is quoted annually on user count, number of modules and how customised the deployment is, because every version upgrade means retesting each customisation. Compare what is included rather than the headline rate.
Response
Response times are defined by severity in the contract. Agreeing the definitions in writing beforehand removes the most common source of support disputes, which is two people using the word “urgent” to mean different things.
System down, or payroll and statutory filing blocked. Everything else waits until it is cleared.
A functional error affecting a business process, with no workaround available to the users.
An error with a workaround available, scheduled rather than dropped into the middle of the day.
Enhancement and change requests, handled on a scheduled queue with a published order.
The response time committed against each severity, and the ticket or hours allowance at each contract tier, are written into your agreement before it is signed.
Inherited systems
This is a large share of the work, and it is worth saying plainly: you do not need to have worked with us before.
Taking over an existing deployment starts with an audit: how the system was configured, what was customised, which third-party modules are installed, what documentation exists and what condition the data is in.
It produces a realistic support price rather than a guess. And it usually surfaces fixable problems the business had quietly accepted as normal.
The audit is a deliverable in its own right. If you decide to keep your current support provider afterwards, you still walk away with a documented picture of your own system.
Training
ERP training fails in a predictable way: one long session at the end of the project, delivered on demo data, to people who have not yet used the system for anything real.
Finance learns the accounting workflow. Storekeepers learn goods receipt and issue. Managers learn approvals and reporting. Nobody sits through the other three.
Sessions run during user acceptance testing, so people practise on transactions and customers they recognise rather than on a demo company.
Written procedures and session recordings, so the knowledge does not leave the business with the one person who attended.
Included as an annual allowance in the support contract. Businesses with high turnover get more from recorded modules than from repeating live sessions.
Training during a rollout is part of the implementation rather than the support contract. ERP implementation →
Migration
Whether the move is to a new platform, a newer version, or off a legacy system nobody supports any more, the sequence does not change. Version upgrades follow the same logic on a smaller scale: migrate the database, retest every customisation against the new release, fix what broke, validate with users, then switch. Heavily customised systems take longer, which is the recurring cost of over-customising in the first place.
Data structures, customisations, integrations and the real condition of the data, before anything is promised about the timeline.
Before anything movesMaster data, opening balances, open transactions, and an honest decision about how much history is worth carrying across.
Signed off in writingThe longest task in almost every migration, and the one that determines whether everything after it works or does not.
The long poleA full load into a test environment, then a parallel run against the system you are leaving, with users on both.
Parallel runBalances must match the source system before anyone signs off. A migration that does not balance costs several times more to correct afterwards than it would have cost to check.
Sign-off gateRepeat the load against live data, in a planned window, with a rollback position written down before the window opens.
Planned windowCoverage
Support is available for deployments we implemented and for systems inherited from another vendor, subject to the initial audit.
OdooSupport, AMC and version upgrades, including deployments we did not build. A dedicated functional and technical team rather than a shared queue.
Microsoft Dynamics 365Finance & Operations: enhancement, integration and upgrade work, with customisations retested each release.
Oracle NetSuiteSaved searches, reporting, subsidiary consolidation and the release-cycle testing NetSuite's twice-yearly upgrades require.
BayzatHR and payroll: configuration changes, WPS handling, leave and end-of-service rules, and the integration into your finance system.
ClearTaxVAT and e-invoicing compliance, kept in step with the ERP as the UAE mandate timetable moves.
ZuperField service management: scheduling, mobile workflows and the link back into work orders and invoicing.
Platform-specific cover: Odoo AMC → Finance & Operations →
How to start
Not sure whether your ERP needs support or replacing? The health check answers that question first, and it is useful either way.
A short review of your current deployment, its configuration and its data. Useful whether or not you end up working with us.
What is working, what is broken, what it would cost to fix, and exactly what a support contract would and would not cover.
An ongoing AMC, a one-off remediation project, a migration, or a training programme. In practice, often a combination.
The health check is where every support relationship here starts, including the ones that begin with a system we have never seen. Book a system health check →
Support FAQs
An ERP support contract typically covers user assistance, bug fixes, report and form changes, minor enhancements, version upgrades and system health monitoring. Response times are set by severity, so a system-down issue is handled differently from a report tweak. New modules are normally quoted separately as projects.
An annual maintenance contract is a yearly agreement covering support and upgrades, priced on user count, number of modules and the level of customisation in your system. Heavily customised deployments cost more to maintain, because every version upgrade requires those customisations to be retested.
Yes. Taking over an existing deployment starts with a system audit: how it was configured, what was customised, what documentation exists and what condition the data is in. That audit sets a realistic support price and usually surfaces fixable problems the business had accepted as normal.
Role-based sessions rather than a single system tour: finance users learn the accounting workflow, storekeepers learn goods receipt and issue, managers learn approvals and reporting. Training runs on your own data during user acceptance testing, so people practise on transactions they recognise. Recorded sessions help with new joiners.
Migration follows the same discipline as an implementation: audit the current system, define what data moves, cleanse it, load into a test environment, reconcile balances, then repeat for the live cut-over. Reconciliation before go-live is non-negotiable, because a migration that does not balance costs far more to fix afterwards.
Response times are defined by severity in the contract. A system-down or payroll-blocking issue is critical, functional errors are high priority, and enhancement requests sit on a scheduled queue. Agreeing these definitions in writing before signing avoids the most common source of support disputes.
Yes. Refresher and new-joiner training is usually included as an allowance of days per year inside the support contract, with additional sessions charged separately. Businesses with high turnover get more value from recorded modules and written procedures than from repeated live sessions.
Support is normally quoted annually, either as a percentage of implementation value or as a fixed figure based on users and modules. Compare what is included rather than the headline rate: whether report changes, version upgrades and training days are covered makes a bigger difference than the number itself.
Talk to a consultant
Book a free 30 minute call with QZ Infomatics in Dubai. You will leave it with a platform recommendation, the reasoning behind it, a realistic timeline and an indicative budget band — before you commit to anything.
