Migrate SharePoint forms

From sharepoint lists and infopath forms to apps on live data.

SharePoint lists with InfoPath forms and designer workflows carried thousands of departmental processes.

SHAREPOINT LISTS AND INFOPATH FORMSSMARTAPPSA listA data handler on the list, or a Lima-owned table where the list was a copyAn InfoPath form with rulesA screen with components, validation and actionsA data connection to the ERPA table handler on the ERP object, read in placeA designer workflowA flow with lanes, criteria and clocksItem-level permissionsAn access policy plus the role's scopeA document libraryFiles kept with the instanceA lookup between listsA query handler joining the objects
What each element of sharepoint lists and infopath forms 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
Lists and librariesthe records, with lookups between lists
InfoPath formsthe screens, with rules and data connections
Designer and Nintex workflowsapprovals, notifications, escalations
Permissionssite, list and item level
Data connectionsto SQL, web services, sometimes the ERP
Document librariesattachments per item
What each becomes

The mapping, element by element

In sharepoint lists and infopath formsIn SmartApps
A listA data handler on the list, or a Lima-owned table where the list was a copy
An InfoPath form with rulesA screen with components, validation and actions
A data connection to the ERPA table handler on the ERP object, read in place
A designer workflowA flow with lanes, criteria and clocks
Item-level permissionsAn access policy plus the role's scope
A document libraryFiles kept with the instance
A lookup between listsA query handler joining the objects
Context

Support end for InfoPath 2013: July 14 2026 (verify against Microsoft's lifecycle page before publishing).

The path

Five steps

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

Illustrative

A life-sciences company inventoried 410 InfoPath forms across 26 sites: 180 were variations of the same 12 requests, 95 were surveys and attestations, 60 were deviation reports. The 12 requests became 12 process apps with site as a scope; the surveys became one survey pattern on the workflow engine; the deviation reports became the nonconformance app, reading the batch and the inspection lot live from the ERP for the first time.

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.