The forms your approvals run on—rebuilt as one system.
Microsoft InfoPath replacement, without losing the rules inside your forms. Microsoft retired InfoPath Forms Services in SharePoint Online after July 14, 2026—we survey every form, rule and data connection, then move them, with the workflows they fed, to one platform.
We rebuild the process, not just the form: the request, the approval, the lookup and the record become one system, checked against the original before anyone switches.
- Every form, rule and connection surveyed
- Submissions checked against the original
- Rehearsed switch, with rollback
// where the seams are
What an InfoPath setup tends to look like
An InfoPath form is rarely just a form. It is the front of an approval process that grew up around it—which is why we don't rebuild it one screen at a time. It goes through the one-system-at-a-time legacy modernization method: survey, mirror, side by side, switch.
A typical setup: a form template published to a SharePoint library, rules and validation inside it, a data connection to a list someone keeps by hand, a SharePoint Designer workflow that emails the approver, and years of submitted forms stored as XML. Rebuild only the form in a new tool and every one of those seams comes with it.
- Requestswere an InfoPath form in a library
- Approvalswere a SharePoint Designer workflow plus email
- Lookupswere a hand-kept list
- Recordswere XML nobody can report on
- Hand-offswere re-keyed into the system that does the work
- Reportingwas an export reworked in a spreadsheet
Before: 5 places the data lives · re-entered by handAfter: 1 platform · entered once
// before and after
A form in a library, or one system for the whole process
With the InfoPath forms
- Forms depend on a service Microsoft has retired in SharePoint Online
- Approvals live in a workflow and an inbox, so nobody sees where a request stands
- Lookup lists are kept by hand and drift out of date
- Submitted forms are XML files nobody can report on
- Approved requests are typed again into the system that does the work
After the cutover
- Requests, approvals and records in one system, in the browser
- Every request shows its status, its approver and its history
- Lookups read from the system of record, not a copied list
- Years of submitted forms, moved and searchable
- The old library kept read-only until you choose to retire it
Not ready for a call? Start with a free check of where your data gets re-keyed: Count your seams
// how it works
How we replace InfoPath forms
The same four steps, with the specifics a library of forms needs.
- 1
Survey
We inventory every form template: where it's published, who still submits it, its views, rules, validation and data connections, and the workflow or person each submission goes to next. Rules hiding in a form get written down in plain language.
- 2
Mirror
We build the new data model and copy submitted forms into it from their XML, on a schedule. Your team keeps working the way it does today; nothing they do changes yet.
- 3
Side by side
The same requests go through both. We compare submissions, approvals and the records they produce until they match, and explain every difference before anyone relies on the new screens.
- 4
Switch
We rehearse the switch on a copy, then move each process on a date you choose. The form library stays read-only, so rolling back is a decision, not a rebuild.
From the first call to the last switch
Each rung of the engagement has one job. Here is what each one means for a library of InfoPath forms.
What we cover
- Which forms your work still depends on
- Where they meet the rest of your systems
- Which process to move first
What we cover
- A walk through the forms and approvals that matter
- The seams traced to the systems around them
- A one-page map you can take to your leadership
What it includes
- A survey of every form, rule and data connection
- A map of where each submission goes and who re-keys it
- A cutover plan with rehearsal and rollback
- The first automation to build once it's unified
- The measure each phase must move
How each phase runs
- The process your work depends on most, first
- A rehearsal on a copy before every switch
- Submitted forms moved and checked against the originals
- Each phase measured before the next begins
The paid pilot
- One seam, taken from start to finish
- A fixed fee, agreed in the Blueprint
- Exit criteria written down before work starts
- Run in your own environment where your requirements call for it
- A decision at the end: continue to the next phase, or stop
Questions about replacing InfoPath
When did Microsoft retire InfoPath?
Microsoft announced in June 2023 that InfoPath Forms Services would be removed from SharePoint Online, in Microsoft 365 and Office 365, for all tenants after July 14, 2026, with no option to extend. Extended support for the InfoPath 2013 desktop client ended on the same date, per Microsoft's lifecycle page.
Sources: Microsoft SharePoint Blog, “Support update for InfoPath Forms Services in Microsoft 365” (June 30, 2023), and Microsoft Lifecycle, “InfoPath 2013”.
Read Microsoft's announcementDo our existing forms still work?
Don't plan on it. Microsoft's notice says that once the service is removed, people can no longer submit new responses through InfoPath Forms Services in SharePoint Online, and designers can no longer publish. Submitted forms can still be opened in the InfoPath 2013 client by anyone with permission to the file. The survey tells you exactly where you stand.
Why not just rebuild each form in Power Apps?
For a simple, standalone form, Microsoft Power Apps may be the right call. But an InfoPath form is usually the front of a process: an approval, a lookup list, a hand-off into another system. Rebuild the screen alone and every one of those seams stays. We map the whole process first, then decide what each form becomes.
What happens to years of submitted forms?
They move with the process. We read the XML behind every submitted form, map its fields to the new records, and copy the history across during the mirror step, checking counts and key values against the originals. The library stays read-only afterwards, so the old forms remain there until you decide to archive them.
We have hundreds of forms—where do you start?
With an inventory, not a rebuild. The survey lists every form, where it's published, who still submits it, its rules and data connections, and what it feeds. Some turn out to be duplicates or no longer used. We group the rest by process and move the ones your work depends on first, a few at a time.
Who does the work?
The owner of UniCorp leads every engagement, from the first call to the last switch, and is accountable for what ships. An AI-assisted engineering team builds it, and every change is tested before it reaches your systems. You meet the people doing the work before you commit.
For IT and security
What your IT team will ask—answered up front.
Each of these is designed to your requirements and agreed in the Blueprint—not a certification we claim to hold.
designed to your requirements
- Where it runs
- Hosted by us or in your own cloud account, decided by your requirements during the Blueprint.
- Sign-in
- Through your identity provider, set up to your requirements, so access starts and ends with your own accounts.
- Roles and audit trail
- Each person sees only what their role allows, and changes to sensitive records are recorded—who, what and when.
- Your data out
- Export in standard formats, such as CSV, whenever you ask—during the engagement and after it.
- Change control
- Every switch is rehearsed on a copy first, with rollback ready. AI-assisted work goes through the same pull request and automated tests as any other change.
- Documentation and handover
- Written as we build, not after, with a handover your team can run with.
- Security review
- We'll answer your security questionnaire.
- License
- You receive a perpetual license to the software we build for you.
Find your constraint. Get capacity back.
A free 30-minute call. We'll name the one constraint holding you back and the fastest path past it—whether or not you work with us.
30 minutes—bring your list of forms, leave with the first process to move.