What is the difference between perpetual and subscription licensing?

Perpetual license: one‑time fee to own the software forever, plus annual maintenance (typically 15‑20% of license cost). Subscription: recurring fee (monthly/yearly) that includes software, support, and often infrastructure. Subscription shifts from CAPEX to OPEX.

What hidden costs should I watch for in ERP licensing?

Common hidden costs: additional modules, implementation services, training, integration, data migration, and maintenance escalations. Always read the fine print.

ERP licensing models

Q: What are named users vs concurrent users?

Named user licenses are assigned to specific individuals. Concurrent user licenses allow a set number of users to access the system simultaneously – any user can log in as long as the total concurrent count doesn't exceed the license limit.

From ERPEDIA, the independent ERP knowledge base

ERP licensing models determine how you pay for software and services. The choice between perpetual and subscription, named and concurrent users, and modular vs suite pricing significantly impacts total cost of ownership (TCO) and financial flexibility. This article explains common models, their trade‑offs, and hidden costs to consider.

Contents

1. Perpetual licensing
2. Subscription (SaaS)
3. Perpetual vs subscription
4. Named vs concurrent users
5. Modular vs suite pricing
6. Other licensing metrics
7. Hidden costs & fine print
8. Choosing the right model

1. Perpetual licensing

Traditional on‑premise model: Pay a one‑time license fee for the right to use the software indefinitely. Plus annual maintenance (typically 15‑20% of license cost) for support and upgrades.

Pros: Predictable long‑term cost, full control, no recurring dependency.
Cons: High upfront CAPEX, upgrade costs, internal IT overhead.

Example: SAP ERP (on‑premise), Microsoft Dynamics AX (legacy), Oracle E‑Business Suite.

2. Subscription (SaaS / cloud)

Pay as you go: Monthly or annual fee per user. Includes software, support, infrastructure, and often automatic upgrades. Shifts cost from CAPEX to OPEX.

Pros: Low entry cost, predictable OPEX, always up‑to‑date, scalable.
Cons: Long‑term cost may exceed perpetual, less control over upgrades, data residency considerations.

Example: Oracle NetSuite, SAP S/4HANA Cloud, Microsoft Dynamics 365 Business Central (cloud), Odoo Online.

3. Perpetual vs subscription comparison

Aspect	Perpetual	Subscription
Upfront cost	High (license fee)	Low (first month/year)
Ongoing cost	Maintenance (15‑20%/year)	Full subscription fee
Total cost (5 years)	Lower if no major upgrades	Higher, but includes upgrades
Upgrades	Paid, major projects	Automatic, included
IT infrastructure	Customer manages	Vendor manages

5‑year TCO example (50 users):
Perpetual: $200k license + $40k/year maintenance = $400k total
Subscription: $120/user/month × 50 × 60 months = $360k total
(Rates vary; always model your scenario)

4. Named vs concurrent users

Named user: License assigned to a specific individual. Used by that person only. Common for full‑time employees.

Concurrent user: License allows a set number of users to access the system simultaneously. Any employee can log in, as long as the total concurrent sessions don't exceed the license count. Good for shift workers or occasional users.

	Named	Concurrent
Best for	Dedicated daily users	Occasional, shift, or part‑time users
Cost efficiency	Simple to count	Can be cheaper if many users but low concurrency
Management	Assign to person	Monitor peak usage

5. Modular vs suite pricing

Modular: Pay for each module (finance, inventory, HR, etc.) separately. You can start small and add later. Common in both perpetual and subscription models.

Suite / all‑in‑one: One price for the entire ERP suite. Often better value if you need many modules, but may include modules you don't use.

Tip: Some vendors offer "user + module" bundles (e.g., finance user costs less than manufacturing user).

6. Other licensing metrics

Revenue‑based: License fee as percentage of company revenue (rare, mostly in micro‑ERP).
Transaction‑based: Pay per invoice, order, or document (common in some verticals).
Storage‑based: Fee based on data volume (in some cloud ERPs).
Device‑based: License by machine (rare today).

7. Hidden costs & fine print

Always read the license agreement carefully. Watch for:

Implementation & training: Not included in license.
Integration fees: Connecting to other systems.
Data migration: Often a separate cost.
Maintenance escalation: Annual increases (e.g., CPI + 2‑4%).
User reclassification: Some vendors audit usage – ensure compliance.
Termination fees: Data extraction costs if you leave.

8. Choosing the right model

Consider these factors:

Cash flow: Can you afford high upfront (perpetual) or prefer OPEX (subscription)?
IT capability: Do you have a large IT team to manage on‑premise?
Growth plans: Subscription scales easily; perpetual may need additional license purchases.
Customisation needs: Perpetual allows deeper customisation (but at cost).
Industry regulations: Some industries require data on‑premise.

Key Takeaways

Perpetual: high upfront, own software, pay annual maintenance.
Subscription: low entry, OPEX, includes upgrades and infrastructure.
Named users for dedicated staff; concurrent for occasional/shift users.
Modular pricing lets you start small; suite can be better value if you need many modules.
Always model TCO over 3‑5 years and read the fine print for hidden costs.

Can I mix perpetual and subscription? Some vendors allow hybrid (e.g., on‑premise core + cloud modules).

What happens if I stop paying subscription? You lose access to the software and data (though you can usually export).

Are there discounts for non‑profit or educational institutions? Yes, many vendors offer special pricing – always ask.

Continue Reading in ERPEDIA

ERPEDIA is maintained by Professionals Lobby as an independent ERP knowledge initiative focused on reducing ERP implementation risk in the UAE and GCC.
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.