Migrate Notes apps

From hcl notes and domino applications to apps on live data.

Notes and Domino applications carried a generation of approvals, requests and registers, each with its own database, its own forms and its own agents.

HCL NOTES AND DOMINO APPLICATIONSSMARTAPPSA Notes form with computed fieldsA screen with components, properties and expressionsA view with a selection formulaA grid on a data handler with a filterA scheduled agentA criterion on records, or an action on a clockAn ACL with reader fieldsAn access policy inherited from the source, plus the role's scopeA mail-routed approvalAn approval flow with levels, alternates, clocks and escalationA replica per siteOne app, read in place, with the site as a scopeDocuments stored in the databaseRows in the system of record, or files kept with the instance
What each element of hcl notes and domino applications becomes in SmartApps.
7
elements mapped
this page
4
catalogue apps most often built on this path
catalogue
1 week
for the inventory
offer
10
apps in the first fixed-price conversion
offer
What you have

The typical inventory

ElementWhat it holds
Databases (.nsf)one per application, often hundreds per company, with replicas per site
Forms and subformsthe screens, with computed fields and hide-when formulas
Viewsthe lists, with selection formulas and categorised columns
Agentsscheduled or triggered code: reminders, escalations, routing
ACLs and roleswho may read, author, edit; reader and author fields
Mail-in and workflowapproval chains built on mail routing
What each becomes

The mapping, element by element

In hcl notes and domino applicationsIn SmartApps
A Notes form with computed fieldsA screen with components, properties and expressions
A view with a selection formulaA grid on a data handler with a filter
A scheduled agentA criterion on records, or an action on a clock
An ACL with reader fieldsAn access policy inherited from the source, plus the role's scope
A mail-routed approvalAn approval flow with levels, alternates, clocks and escalation
A replica per siteOne app, read in place, with the site as a scope
Documents stored in the databaseRows in the system of record, or files kept with the instance
Context

HCL continues to sell and support Notes and Domino; the reason to move is the duplicate data, the aging forms and the skills, and the moment is usually a platform contract or an ERP change.

The path

Five steps

InventoryOne week; every element above listed with its owner and its last change.
A move

Illustrative

A manufacturer kept 340 Notes databases, 60 of them still in daily use. The inventory grouped the 60 into 14 app types: 22 were request-and-approval forms, 11 were registers of equipment or suppliers that duplicated the ERP, 9 were escalation agents around late deliveries. The registers were retired in favour of screens on the ERP objects; the requests became process apps; the escalation agents became one data-driven app. The first ten apps were rebuilt in six weeks and the 60 in a quarter.

illustrative · figures for the shape of a typical move
Apps most often built on this path

Questions

What if an application has logic worth keeping?

It becomes a registered function the app's actions call by name, with its inputs and outputs logged.

Who owns the new apps?

The process owner, with the configurator role; the application team keeps the gates and the write-back switches.

What does it cost?

The inventory is fixed-scope; the first ten apps carry a fixed price written before the work; the platform is priced by capacity with apps included.

Start with a one-week inventory

We list the applications, the forms and the workflows you run today, group them by the app type they become, and write a fixed price for the first ten before any work begins.