Benefits of the update for the customer

The strongest reason to update isn’t novelty, but continuity on a better foundation.

An iCMS 3.1 site often contains industry-specific information and expertise accumulated over the years: content structures, user roles, customized modules, forms, integrations, business rules, internal workflows, and established content production practices. Replacing them with a general-purpose CMS can mean losing that value or having to rebuild it in another system.

The iCMS 4.0 update is designed to preserve the essentials and improve the platform around them.

Customers get:

• A more modern admin experience for content creators and administrators.
• More structured content editing, better page template tools, shared dialogs, and rich-text editing integrated with the media library.
• Better capabilities to manage custom data via the Managers Framework.
• Easier management of users, groups, inherited permissions, media permissions, and fine-grained permissions.
• Authenticator app–based MFA for stronger protection of user accounts.
• A stronger API foundation for integrations, external interfaces, and modern workflows.
• Unified integration management instead of individual custom scripts.
• Better visibility into background imports and exports, translation jobs, synchronizations, AI functions, and other long-running tasks.
• Real-time browser updates for selected administration and custom function workflows.
• More systematic multilingual content management and translation review.
• Managed AI assistance, where AI-generated changes can be reviewed before being applied to published content.
• A natural opportunity to renew the visual identity, content structure, navigation, page templates, and mobile experience at the same time.

A more modern everyday tool

For content creators and administrators, the most visible change is the day-to-day user experience.

iCMS 4.0 supports more unified admin views, clearer module-specific workspaces, shared dialogs, more advanced rich text editing, image and link workflows integrated with the media library, automatic form saving, and better management views for redirects, logs, translations, integrations, users, groups, and background tasks.

The goal isn’t just a more modern look. The goal is a system that feels easier to manage and more reliable to the people who use it every day.

Stronger permission management and user account protection

iCMS has long supported permission levels, group-specific rights, default rights, and inherited rights. iCMS 4.0 improves the manageability of these features and expands them with more granular permission options.

This is important in member services, intranets and extranets, customer portals, learning environments, private media libraries, and operational systems where different users need different rights.

iCMS 4.0 also adds authenticator app–based MFA, commonly known as two-factor authentication or 2FA. It enables stronger protection of administrator accounts and the accounts of selected user roles.

Better support for integrations and automation

iCMS 4.0 treats integrations as a shared feature of the platform. Connection details, integration keys, activity history, provider-specific settings, queues, diagnostics, and HMAC-signed system-to-system authentication are all managed through shared structures.

As a result, integrations are easier to design, maintain, and monitor.

Background tasks can also be surfaced more visibly and managed better. TaskTimer can handle scheduled and long-running tasks such as imports and exports, synchronizations, media processing, translation jobs, AI functions, mass updates, and recurring site-specific tasks. In iCMS 4.0, task status, logs, requeue management, and status tracking via the API make these processes more visible to both administrators and interfaces.

AI without losing control

AI can save time in content production, translation work, and administrative tasks, but in business systems its use needs clear boundaries and control mechanisms.

iCMS 4.0 is designed to support governed AI workflows. AI features, activity records, queues, object-specific triggers, review states, and functions related to deploying changes make it possible to prepare and review AI-generated content before it alters data in production.

This differs from simply adding an AI button to the interface. iCMS integrates AI-assisted work with the same object, permission, and review model as the platform’s other functions.

What the customer retains

The update should be understood as modernization, not abandonment of the old system.

Existing iCMS customers retain the most valuable part of their current system: the business knowledge already embedded in their implementation. The current content, data structures, custom concepts, user needs, permission rules, integrations, and workflows form the starting point for the 4.0 update.

Every migration still requires a project-specific analysis. Themes, page templates, custom modules, old helper structures, integrations, media, and data flows must be reviewed and updated. Some legacy practices are worth simplifying rather than copying as-is.

The goal, however, is not to rebuild the customer’s digital service from scratch. The goal is to carry the useful parts of the current service forward onto a better-maintained platform.

Why not simply continue using iCMS 3.1?

iCMS 3.1 has served customers for a long time, but it is not the right long-term platform version for current and future requirements. Active support for iCMS 3.1 is planned to end at the end of 2026, so current managed SaaS customers should view the 4.0 update as the recommended maintenance and modernization path.

Short-term transitional maintenance may still be justified while planning the update. For long-term security, compatibility, platform support, account protection, integrations, APIs, mobile-friendly administration, AI readiness, and future development, however, iCMS 4.0 provides a stronger foundation.

When another platform can be a sensible alternative

iCMS is at its strongest when the site is also a digital service. If a customer intentionally wants a simple brochure website with very little custom data, little workflow logic, no significant need for permission management, no integrations, and no business-specific functionality worth preserving, another website platform may be a justified alternative.

For many current iCMS customers, however, the stronger business option is to modernize the service on the iCMS 4.0 platform. This preserves the current investment, keeps the customer within the maintained iCMS platform, and at the same time opens a practical path to a better content creation experience, a renewed public-facing appearance, stronger integrations, more advanced permissions, MFA authentication, APIs, multilingual workflows, automation, and governed AI assistance.

Practical update planning

A good iCMS 4.0 update starts by identifying what is essential in the current service.

Key questions include:

• Which features of the current iCMS 3.1 system are critical to the business?
• Which custom modules or workflows should be preserved?
• Which content, page structures, and media should be migrated as-is, and which should be renewed?
• What kinds of permission rules does the system have today, and where is simpler or more granular management needed?
• For which user roles should authenticator app–based MFA be enabled?
• What integrations does the system have today, and what new integrations are planned?
• Which long-running tasks need clearer status tracking, log data, progress tracking, or requeue management?
• Which multilingual content requires a translation review process?
• Which AI-assisted workflows would save time if they could be used in a governed way and their results reviewed?
• Which visual themes, page templates, and mobile views should be renewed as part of the update?

The end result should be more than a technical migration. It should be a deliberate modernization of the entire service.