Notes databases, Access files, spreadsheet-and-email processes, InfoPath forms, aging BPM suites and custom code all carry processes worth keeping and copies of data worth retiring.
Notes and Domino applications carried a generation of approvals, requests and registers, each with its own database, its own forms and its own agents.
Read the path →Access databases grow where a team needed a form and a report faster than IT could provide them.
Read the path →Many processes run on a spreadsheet and an email thread: a request in a workbook, a chain of replies, a final version typed into the ERP.
Read the path →SharePoint lists with InfoPath forms and designer workflows carried thousands of departmental processes.
Read the path →A BPM suite bought a decade ago still runs the processes it was bought for, with its own data store, its own forms and a per-user licence.
Read the path →Custom-coded internal applications, a Java portal, a .NET approval tool, a Python script with a web page, work until the person who wrote them leaves.
Read the path →The inventory takes a week. The first ten apps take four to eight weeks depending on their size; the catalogue's per-app estimates apply. Large estates run in waves of ten.
Copies of ERP data are retired; the app reads the ERP. The tool's own records are exported and either loaded into a Lima-owned table with lineage or archived.
Screens are composed from the same fields, so the layout can follow the old form; most owners take the drafted layout and adjust labels.
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.
