Power Accelerate

Hard Deadline

Microsoft retires InfoPath Forms Services on 14 July 2026. After that date, browser-rendered InfoPath forms in SharePoint Online stop working. You can't kick this can any further down the road.

Expertise Gone

InfoPath Designer was discontinued in 2014. The teams who built these forms have moved on or retired. Each month of delay means more institutional knowledge lost, and more forms whose business logic only lives in someone's head.

Manual Migration Doesn't Scale

Rebuilding forms one-by-one in Power Apps, SharePoint Lists, or modern web stacks is slow, error-prone, and expensive. Average effort per non-trivial form: 30–80 hours. Multiply by the size of your estate.

Years of Submissions

The forms aren't the problem - the data is. Years of submissions sitting in SharePoint libraries, attachments, audit history, workflow state. None of it is going to migrate itself, and most of it won't survive a sloppy export.

Archive

For templates whose forms are no longer actively submitted but whose data must survive. Compliance retention, audit trail, regulator handover. Submissions, attachment URLs, and workflow history are extracted to a queryable SQLite archive - no rebuild needed.

Typical signals: no submissions in the last 12 months, stale workflow associations, no active publish history.

Lift

For templates with simple structure but ongoing use. Flat schema, a couple of views, light validation rules, no code-behind. These map naturally to SharePoint Lists, Power Apps canvas, or a Lists Designer-style replacement - fast, lightweight, no over-engineering.

Typical signals: small T-shirt size, fewer than ~30 fields, no managed code, minimal repeating sections, single deployment.

Rebuild

For forms with real business logic that need to keep working. Code-behind, complex rules, web-service data connections, workflow integrations, multi-view orchestration - the kind of form where "just export the data" would lose 80% of what makes it useful. AI rebuilds the full application on the platform of your choice, data included.

Typical signals: managed code-behind, multiple data connections, dozens of rules, repeating sections, multi-deployment footprint.

Submissions & Fields

Every submitted form, parsed against its template schema. Field values, repeating-group rows, computed fields, multi-select choices - preserved with original structure intact, one row per submission per deployment.

Attachments & Inline Images

Attachment metadata (filename, size, content type, source URL) captured for every submission. Bytes stay in SharePoint as URL pointers by default - opt-in to materialize them locally as a content-addressed blob store.

SharePoint Metadata

List columns, submitter identity, created/modified timestamps, content-type associations, version history - pulled from the SP REST + Graph endpoints alongside the form XML, joined into the same record.

Workflows & Audit Trail

SPD workflow associations and instance history captured per form. Optional audit-trail extraction surfaces signer identities, view events, and edit lineage for compliance handovers.

Design Elements

The full template manifest - schema, rules, views, connections, code-behind - captured alongside the data so AI rebuild has complete context, not just a column list.

Portable Output

One SQLite database per export run, one table per deployment, one row per submission. Plus a Markdown manifest documenting every column. Queryable, archive-grade, target-platform-agnostic.