TIBCO Nimbus product retirement

Move from Nimbus and keep working in UPN

TIBCO retired Nimbus in 2025, so your process maps and their documents need somewhere to go. We delivered Nimbus to a number of customers. Today we deliver Elements.cloud, and we help you move, Document Registry included.

A top-level process map in TIBCO Nimbus above a top-level process map in Elements.cloud, where the activities carry ISO, KPI and GDPR tags
The dates

What TIBCO announced, date by date

The retirement notice was first published on 2 August 2024. Customers who moved from Cloud Nimbus to the on-premises version could renew for a further 24 months, to September 2027, and have to request extended support from TIBCO for that period.

2 Sep 2024
Nimbus closed to renewals and new subscriptions
1 Sep 2025
TIBCO Nimbus on-premises retired and its support ended
31 Oct 2025
TIBCO Cloud Nimbus and TIBCO Nimbus Service retired
Sep 2027
Latest end of extended support for renewed on-premises licences
Why Elements.cloud

Why we deliver Elements.cloud today

  • Your authors already know the notation — Elements.cloud uses the same Universal Process Notation. It is easy to learn and easy for end users to understand, and your process authors keep their skills.
  • It works with M‑Files — Elements.cloud integrates with the other platforms we deliver, M‑Files among them, so the process diagrams and the documents they govern stay connected.
  • Visual processes inside a QMS — An integration between Elements.cloud and VisualQMS puts visual business processes inside a complete quality management system.
The Elements.cloud editor with a process being drawn: activity boxes with the roles that perform them, the shapes panel and the toolbar
Migration

What you can take with you from Nimbus

We have implemented business process management solutions for more than ten years. How much can be migrated depends on your maps, so the plan comes first.

  1. Decide what is worth moving

    You, with Solution Management

    Together we decide which parts make sense to migrate and which should be renewed.

  2. Migrate the maps that can move

    Elements.cloud

    Nimbus process maps can be migrated to Elements.cloud, and the plan says which ones move as they are.

  3. Renew the rest

    Process authors, with the AI in Elements.cloud

    The other maps are redrawn in UPN, or derived from text such as SOPs with the AI in Elements.cloud.

  4. Move the Document Registry

    Solution Management

    If your Nimbus maps link to documents in the Document Registry, we help move the documents and links to M‑Files.

  5. Maps and documents stay linked

    M‑Files manages the governance documents as the replacement for the Nimbus Document Registry.

Plan the move from Nimbus with us

Elements.cloud

What your process authors work with

We are an official reseller of Elements.cloud, for process mapping and for use in quality management systems, and we offer consultancy on it.

Draw in the notation you know

Process maps in UPN, with resources and roles on the activities and graphical elements for the look and feel.

Documents linked from the activity

Documents are linked from the activities in a process through the Elements.cloud URL library.

ISO 9001 tagged where it applies

Reference models such as ISO 9001 are used in the maps and tagged on the activities they apply to.

Approved before it is published

Editing happens in draft. Review and approval follow, and then publication to end users.

Your maps inside M‑Files

M‑Files serves as the document registry, and the process maps are shown inside M‑Files.

Already on Elements.cloud

Add a controlled document registry

If you already use Elements.cloud and need a controlled place to create, review and approve documents and link them to the process diagrams, M‑Files is that registry. We build it from pre-configured solutions that can be adapted, and we can start quickly with a pilot. The integration with Elements.cloud is built by our development partner CtrlDocs, named M‑Files Solution Partner of the Year 2025.

Three screens from M-Files: a list of published procedures and policies with their next review date and approver, the version history of one procedure, and that document's metadata card with its approver and dates
Published procedures with their review dates, one document's version history and its metadata card.
M‑Files and Elements.cloud

A full replacement for the Document Registry

M‑Files, with the integration to Elements.cloud from our development partner CtrlDocs, covers what you used the Nimbus Document Registry for.

Write documents in Microsoft Office

Documents are created in Microsoft Office, and M‑Files keeps the versions.

Review and approval in separate steps

Review, quality review and approval are separate steps.

Procedures published when approved

A procedure is published once it has been approved.

Workflows that follow your process

The workflows are configured to your document process.

Grouped by region, area or department

Documents are grouped by metadata such as region, process area and department, among many others.

Access decided by the metadata

Permissions can be based on any of the metadata.

Document links are published to the Elements.cloud URL library automatically.

Diagrams open inside M‑Files

Process diagrams from Elements.cloud are rendered inside M‑Files.

In Microsoft Teams as well

M‑Files content, process diagrams included, is shown in Microsoft Teams.

VisualQMS

See what answers each requirement

VisualQMS shows quality information in the context of the requirements the company must live up to. For each requirement you see the guiding documents, process diagrams and quality activities that answer it, and where a requirement is not sufficiently backed up.

  • Start from the documents — The guiding document view starts from policies, procedures, instructions and guidelines.
  • Modules for the quality department — The quality activities are modules for the quality department's own work, with standardised workflows, scheduling, reminders and notifications.
Three screens of VisualQMS: the statements of ISO 9001 listed as a tree, a CAPA board with each CAPA in the column of its workflow state, and the metadata card of one CAPA with its scope, its non conformance and its description
Next step

Show us your Nimbus maps

Tell us roughly how many maps you have and whether they link to documents in the Document Registry. We introduce you to Elements.cloud, and to M‑Files as the replacement for the registry. Email sales@solutionmanagement.eu or call +45 2141 6100. We answer the same working day.

Questions about leaving Nimbus

Can all our Nimbus maps be migrated?
To a certain extent. Existing Nimbus process maps can be migrated to Elements.cloud, and how much depends on the maps. We help you plan the migration and decide which parts make sense to migrate and which should be renewed. Maps that are renewed are redrawn in UPN, or derived from text such as SOPs with the AI in Elements.cloud.
What happens to the documents in the Document Registry?
If your Nimbus maps link to documents in the Document Registry, we help move the documents and the links to M‑Files. M‑Files then manages the governance documents as the replacement for the Nimbus Document Registry.
Which products make up the replacement?
Elements.cloud for the process maps and M‑Files for the documents. The integration between them comes from our development partner CtrlDocs. CtrlDocs for Elements publishes approved PDFs from M‑Files to the Elements.cloud URL library, and CtrlProcesses shows the process diagrams inside M‑Files and in Microsoft Teams. We resell all of them.
What did TIBCO announce about Nimbus?
TIBCO closed Nimbus to renewals and new subscriptions from 2 September 2024, retired the on-premises product and ended its support on 1 September 2025, and retired TIBCO Cloud Nimbus and TIBCO Nimbus Service on 31 October 2025. Extended support, for customers who moved to the on-premises version and renewed, runs at the latest to September 2027 and has to be requested from TIBCO.
What should a Nimbus alternative keep?
The notation, the document registry and the link between them. Elements.cloud uses the same UPN, so your authors keep their skills and your readers keep maps they understand. The Document Registry is replaced by M‑Files, where documents are drafted, reviewed and approved, and CtrlDocs for Elements, from our development partner CtrlDocs, publishes the approved PDF to the Elements.cloud URL library, so each activity still opens its procedure. In daily work the diagrams open inside M‑Files and in Microsoft Teams through CtrlProcesses.
How much usually migrates?
It depends on the maps, and we assess yours first. Together we go through what you have, decide which parts make sense to migrate and which should be renewed, and set the plan from that. Maps that are renewed are redrawn in UPN or derived from text such as SOPs with the AI in Elements.cloud. We do not quote a share before we have seen the maps.
Can we stay on Nimbus until 2027?
Only on the on-premises version, and only with extended support. TIBCO's notice allowed customers to move from Cloud Nimbus to the on-premises version and renew for a further 24 months, to September 2027, and those customers have to request extended support from TIBCO. Cloud Nimbus itself was retired on 31 October 2025. Extended support buys time to plan the move; the move itself starts with the same assessment of your maps whenever it begins.