InfoPath End of Life 2026: The Complete Guide to Migrating Off InfoPath

InfoPath End of Life Timeline: May 18 and July 14, 2026

InfoPath was on a long, public glide path. Microsoft stopped active development in 2014. Extended support kept the product alive while customers planned alternatives. The 2026 timeline closed the window across two milestones that affected different parts of the environment in different ways.

May 18, 2026: InfoPath Form Publishing Blocked

This is the date most external coverage missed. On May 18, 2026, Microsoft began blocking the publishing of new InfoPath forms and updates to existing InfoPath forms across every Microsoft 365 tenant. The block applied to all Microsoft 365 environments, including GCC and GCC High.

A designer could still open InfoPath Designer 2013 on a workstation and edit a form file locally, but the publish action into SharePoint Online no longer completed. Existing published forms kept working. End users could still open them, fill them in, and submit them. Forms could not be patched, modified, or replaced through SharePoint Online.

If a business rule needed to change between May 18 and July 14, the only path forward was to rebuild that form on a replacement platform. The failure mode shifted well ahead of the final retirement date. The fix for a broken InfoPath form stopped being an InfoPath fix. It became a migration.

July 14, 2026: InfoPath Forms Services Removed

On July 14, 2026, the following took effect across Microsoft’s InfoPath surface:

• InfoPath Forms Services were removed from SharePoint Online for all tenants. Existing forms no longer open, submit, or render in SharePoint Online lists, libraries, or content types.
• Configuration capabilities were removed from the SharePoint Admin Center. Custom InfoPath forms can no longer be created or modified.
• InfoPath 2013 reached the end of its extended support period.
• Extended support for InfoPath Forms Services on SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition ended.
• SharePoint Server 2016 and SharePoint Server 2019 themselves reached the end of extended support on the same date. For on-premises customers, the entire farm became unsupported, not just the forms layer.
• SharePoint Designer 2013 retired on the same day, so InfoPath forms and paired legacy workflows lost support at exactly the same time.
• The SharePoint 2010 workflow engine retired on the same date. SharePoint Server Subscription Edition kept SharePoint 2013-based workflows beyond July 14 only via the new SharePoint Workflow Manager (a separate Microsoft product), not the legacy engine.

What Does InfoPath Retirement Mean for SharePoint On-Premises Customers?

Cloud-only InfoPath deployments hit a sharp cutoff. On July 14, the forms stopped working. The path forward is clean, even if the migration is hard. SharePoint on-premises customers have a more complicated picture.

InfoPath forms on SharePoint Server 2016, 2019, or Subscription Edition did not stop loading overnight. They keep rendering. They keep accepting submissions. Microsoft no longer issues security patches, compatibility fixes, or bug fixes for InfoPath Forms Services. SharePoint Server 2016 and 2019 themselves lost Microsoft support on the same date. Future Windows updates, browser updates, or SharePoint cumulative updates can break form rendering or business logic silently.

For Government, Healthcare, and Banking organizations, this is the bigger problem. Running production business processes on Microsoft-unsupported infrastructure is a compliance finding. Auditors do not accept the argument that the software still functions. CMMC, FedRAMP, HIPAA, and PCI DSS frameworks all require vendor-supported platforms for production workloads. The day after July 14 was the day the audit clock started on the InfoPath deployments, even if no end user noticed anything different.

On-premises customers also carry two parallel problems: the InfoPath migration and the SharePoint Server migration. SharePoint Server Subscription Edition is the supported path forward for organizations that need to stay on-premises. The realistic plan addresses both projects in coordinated phases, not sequentially.

Can You Still Use InfoPath After July 14, 2026?

In SharePoint Online, no. Forms no longer open, submit, or render. SharePoint Admin Center options for InfoPath were removed.

On SharePoint Server 2016, 2019, and Subscription Edition, yes, in the narrow sense that existing forms still load and accept submissions. But Microsoft no longer issues security patches, compatibility fixes, or bug fixes for InfoPath Forms Services, and the underlying SharePoint Server versions are themselves out of support. Every Windows update, browser update, or SharePoint cumulative update from here on can silently break form rendering or business logic. Running production workloads on unsupported software is a compliance finding under CMMC, FedRAMP, HIPAA, PCI DSS, and most cyber insurance policies.

The technical answer is yes on-premises. The operational answer, for any organization with an audit trail to defend, is no.

Is It Too Late to Migrate Off InfoPath?

No, but the work is harder now than it was six months ago. Three pressures tightened after July 14, and they keep tightening.

Implementation capacity is finite

Implementation partners with deep InfoPath experience are working through a fixed pool of migrations. Capacity tightened as the deadline approached, and post-deadline migrations also lost access to the optional pre-cutover phases (assessment, parallel run, structured user training) that make adoption stick. Rush quotes may carry rush rates.

Data extraction gets harder, then very hard

Before July 14, InfoPath data and templates could be downloaded from SharePoint libraries via the SharePoint Admin Center. After July 14, those Admin Center options were removed. Existing form templates (.xsn files) and form data (.xml files) can still be opened locally, but only through InfoPath 2013 on a workstation that still has it installed and file permissions to the source library. Every quarter that passes makes that legacy toolchain harder to source, license, and run, particularly in environments where new device images no longer ship Office 2013-era components.

Hidden dependencies surface late

Most InfoPath deployments are not pure InfoPath. They are InfoPath forms feeding SharePoint Designer workflows, often paired with Nintex on top, with downstream connectors into Exchange, Active Directory, on-premises file shares, or external systems. When InfoPath software retired, the foundation underneath those workflows shifted too. Teams that scope the migration as “just the forms” usually find the workflow rebuild halfway through the project. The earlier the dependency map is built, the smaller the surprise.

InfoPath Migration Mistakes That Add Months to a Project

Three patterns to avoid, from migration projects that hit walls late in the cycle and had to be partially redone.

Replacing forms-only without the workflow

An InfoPath form is rarely an island. It is usually the entry point of a SharePoint Designer workflow, a Nintex process, or an Exchange routing flow. Teams that scope the project as “swap the forms” rebuild the visible layer and discover the connecting tissue still depends on the retired engine. The right scope is forms plus workflows plus the downstream connectors that feed them. Treating any layer as out of scope creates a second migration project.

Treating post-retirement operation as sustainable

On-premises forms still render. Nothing visibly broke on July 15. That combination tempts teams to leave the deployment alone and revisit later. The problem is that the compliance clock started the day extended support ended, not the day a form fails. Auditors, cyber insurers, and internal risk teams treat unsupported infrastructure as a live finding regardless of whether it is currently functioning. The longer the delay, the harder the eventual conversation with whoever signs off on the risk register.

Assuming Power Apps is a like-for-like replacement

Microsoft’s recommended path is to combine Power Apps for forms, Power Automate for workflows, and Microsoft Forms for lightweight collection. That works for some teams. For organizations that built real business applications on InfoPath, the gap between “three Microsoft products stitched together” and “one platform that replaces what InfoPath did” is meaningful. Power Apps does not run on SharePoint Server 2016, 2019, or Subscription Edition. Teams whose deployments include on-premises and cloud environments cannot use Power Apps as the unified destination. The right replacement decision is made after mapping the actual environment, not from the assumption that the Microsoft default fits.

What Should You Replace InfoPath With?

Microsoft does not offer a one-to-one InfoPath replacement. The market has filled the gap with platforms of different shapes. Four are commonly shortlisted when scope includes both forms and workflows, both cloud and on-premises.

1. NITRO Studio by Crow Canyon Software

NITRO Studio is a no-code/low-code Application Builder Platform purpose-built for Microsoft 365 and SharePoint. It is the platform Crow Canyon has built and refined since 1999, and the platform Crow Canyon uses to migrate organizations off InfoPath today. Crow Canyon Software is headquartered in California. Over a thousand organizations run on NITRO Studio, including the State of California Franchise Tax Board, US Department of Justice, Office of Naval Intelligence, Ballad Health, FSU Credit Union, National University of Singapore, University of Houston, Ventura Foods, AstenJohnson, and Air Wisconsin.

Where it fits:

• Microsoft 365 and SharePoint organizations in Government, Healthcare, Banking, and other industries where security matters
• Teams that need forms, workflows, portals, dashboards, list views, reports, and a clean connection with other purpose-built business applications available from Crow Canyon
• NITRO Studio supports SharePoint On-Premises in two modes, Normal Mode connected to Crow Canyon’s Azure and a fully air-gapped mode through NITRO Secure, and SharePoint Online / Microsoft 365 with the NITRO Studio Engine hosted in Crow Canyon’s Azure (Shared), the customer’s own commercial Azure (Dedicated), the customer’s Microsoft GCC, or the customer’s Microsoft GCC High.
• Buyers who want flat, predictable pricing instead of per-form, per-flow, per-process, or per-connector meters

What it covers:

• Drag-and-drop form designer with cascading lookups, conditional rules, validations, and permissions at the field level
• Workflow manager with approvals, parallel branches, timers, SLAs, and escalations
• Purpose-built business applications available from Crow Canyon as separately licensed add-ons built on NITRO Studio: IT Help Desk, HR Help Desk, Purchasing, Asset Management, Work Orders, and more
• The entire application layer: dedicated user portals, executive dashboards, custom list views, and graphical reports right inside SharePoint
• NITRO Copilot AI features (AI-generated emails, AI-powered workflows) on cloud deployments
• A structured InfoPath migration delivered as a Crow Canyon professional service, which tracks form inventory, conversion status, and cutover progress

Pricing:

Starts at $5,988 per 100 users per year for the NITRO Studio license. Flat rate. Unlimited forms. Unlimited workflows. No usage overages or surprise fees. No AI usage credit fees from Crow Canyon. Organizations integrating third-party AI models (for example, GPT) may have separate usage costs from those providers. Pricing varies by deployment (on-premises and cloud have different SKUs); contact Crow Canyon for deployment-specific pricing.

2. Microsoft Power Platform (Power Apps, Power Automate, and Microsoft Forms)

Microsoft’s recommended path. The full Microsoft path combines Power Apps for forms, Power Automate for workflows, and Microsoft Forms for lightweight data collection. Power Apps handles the form-building layer. Power Automate handles the workflow layer. The combination is well-documented and tightly integrated with Microsoft 365.

Where it fits:

• Cloud-first organizations already standardized on Microsoft 365
• Teams with developer support, comfortable working in Power Fx, Dataverse, and connectors
• Use cases where the application layer and the workflow layer are roughly equal in complexity

Where it falls short:

• No native deployment on SharePoint Server 2016, 2019, or Subscription Edition. Organizations that need to keep any portion of the environment on-premises cannot use Power Apps as the unified destination.
• Per-user, per-flow licensing means costs climb with usage. Premium connectors, Process Mining, and AI Builder are separate add-ons.
• Power Apps Premium is $20 per user per month. Power Automate Premium is $15 per user per month (Microsoft published pricing). Stacked for a typical InfoPath replacement scope, the math lands at roughly $42,000 per year for 100 users. The $12 per user volume tier requires a 2,000-seat minimum, which is outside the typical mid-market and government buyer profile.
• Building a complete business application means stitching Power Apps, Power Automate, Microsoft Forms, and often Power BI together. The learning curve on Power Fx and Dataverse is real.
• Power Platform functionality is reduced in GCC and GCC High environments. NITRO Studio’s is not.

For a full breakdown, see the NITRO Studio vs Power Apps comparison.

3. FlowForma

FlowForma is a no-code process automation platform with strong content presence in the Nintex replacement and InfoPath replacement space. Headquartered in Dublin with offices in New York and London.

Where it fits:

• Mid-sized cloud organizations running a small number of well-governed processes
• Industries like construction, healthcare, and finance, where audit and governance features are central to the buying decision
• Teams that want to write workflows in business-readable steps rather than developer logic

Where it falls short:

• Process-based licensing. The Essentials plan starts at $28,164 per year for up to 3 processes. The Professional plan is approximately $39,516 per year for up to 30 processes. Process counts grow faster than buyers expect. That is roughly five times the cost of NITRO Studio’s flat-rate license for a comparable migration.
• Cloud only. No support for SharePoint on-premises, GCC High, or air-gapped environments. For regulated industries that require those environments, this is a dealbreaker.
• Forms and workflow-centric. For organizations that need a full application platform with portals, dashboards, list views, and pre-built business applications, FlowForma covers part of that scope, not all of it.

4. Plumsail Forms

Plumsail Forms is a focused SharePoint forms product from a Latvia-based vendor. Well-regarded by SharePoint developers for customization depth, particularly the JavaScript and CSS hooks that let teams extend forms beyond default behavior.

Where it fits:

• Teams that already have SharePoint developer skills and want a forms layer that exposes hooks into JavaScript and CSS
• Small to mid-sized deployments where the scope really is forms-only
• Organizations on SharePoint Online or SharePoint Server 2019 / Subscription Edition

Where it falls short:

• Forms-focused product, not a full application platform. Workflow, portals, dashboards, and business applications come from other Plumsail products or external tools.
• No support for SharePoint Server 2016 on-premises. Organizations still on SharePoint Server 2016 (a meaningful share of regulated environments) need a different path.
• Plumsail Forms is licensed as a flat subscription per tenant domain for cloud deployments (unlimited users and forms). On-premises deployments use a per-Web Front End (WFE) server model with separate annual maintenance renewals and standalone development licenses to build and test forms safely.
• Advanced customization often requires developer skills in JavaScript, which sits closer to a developer tool than a no-code/low-code platform for business users.
• Plumsail’s cloud automation connectors are completely unavailable within GCC High environments. Plumsail Forms can be installed in GCC High via manual App Catalog upload, but automation connectors do not function there.

InfoPath Replacement Comparison Table

*Power Platform functionality is reduced in GCC and GCC High environments compared to commercial Microsoft 365.
†Plumsail Forms can be installed in GCC High via manual App Catalog upload, but cloud automation connectors do not function there.

How to Migrate From InfoPath: An Eight-Step Playbook

This is the framework Crow Canyon uses for InfoPath migrations. It applies whether the destination platform is NITRO Studio or another option. The work is the same. The platform changes what “rebuild” looks like.

Step 1. Inventory every InfoPath form in the environment

Most organizations underestimate how many InfoPath forms they have. Forms live in obvious places (HR onboarding, finance approvals, IT requests) and unobvious ones (one-off departmental forms built by a former employee years ago and still in active use). Microsoft provides the Microsoft 365 Assessment Tool to scan a tenant for InfoPath usage. Crow Canyon provides PowerShell scripts that read InfoPath forms on the SharePoint server and output the inventory to CSV. Either approach is fine. The point is to have a complete list before scoping the migration.

Step 2. Categorize forms by business criticality and complexity

Not every form deserves the same effort. A single-page departmental survey used twice a year is not in the same category as a multi-stage purchase request that touches three approval levels. Split the inventory into three buckets: retire (the form is no longer used), simplify (rebuild with reduced scope), and full rebuild (replicate the existing functionality).

Step 3. Map data connections and workflow logic

InfoPath forms rarely live in isolation. Most pull data from SharePoint lists, push data to external systems, or trigger SharePoint Designer workflows on submission. Document every data connection, every workflow trigger, and every external integration before rebuilding. This is the work that surfaces hidden dependencies and prevents the forms-only anti-pattern.

Step 4. Choose the destination platform

By this point, the inventory and the dependency map make the platform decision sharper. If the deployment is entirely cloud and the team has Power Platform skills, Power Apps, and Power Automate may fit. If the scope is forms-only on SharePoint 2019 or Subscription Edition, Plumsail Forms is workable. If there are fewer than thirty cloud-only processes and price isn’t a concern, FlowForma may be worth a demo. If the deployment includes on-premises and cloud, NITRO Studio is the option that covers SharePoint On-Premises (connected or air-gapped via NITRO Secure) and SharePoint Online / Microsoft 365 (with the engine hosted in Crow Canyon’s Azure (Shared), your own commercial Azure (Dedicated), your Microsoft GCC, or your Microsoft GCC High) under one platform and one license.

Step 5. Rebuild forms and workflows on the destination platform

This is the step most teams scope as “the migration,” but it is one of eight, not the entire project. On NITRO Studio, rebuilds reuse the same SharePoint constructs (lists, libraries, permissions, content types) that InfoPath uses, which keeps the timeline shorter than a paradigm shift to Power Platform. Most NITRO Studio customers reach go-live within approximately three months on this step, though the actual time varies with the volume of forms and the depth of workflow logic in scope.

Step 6. Test, validate, and run in parallel

Run the new forms and workflows in parallel with InfoPath for a defined period. Compare outputs side by side. Validate that every business rule survived the rebuild. Get sign-off from the process owners of each process before the cutover. This is the step that catches the “we forgot about that form” surprise before it becomes a production incident.

Step 7. Extract InfoPath form data and templates

Once the replacement is built and validated in Step 6, extract the InfoPath form data (.xml files) and templates (.xsn files) from SharePoint libraries. For teams that started this work before July 14, 2026, the SharePoint Admin Center provided the extraction path. Post-retirement, those Admin Center options were removed, and the remaining access path is InfoPath 2013 running locally on a workstation that still has it installed. Crow Canyon’s professional migration services track this extraction step alongside the rebuild work.

Step 8. Cut over and decommission InfoPath

Switch users to the new platform. Archive InfoPath data per the organization’s retention policy. Remove InfoPath form templates from SharePoint libraries. Document the cutover in the change log.

How NITRO Studio Replaces InfoPath, End to End

NITRO Studio is built around the same SharePoint constructs InfoPath uses. Lists, libraries, permissions, and content types. The forms layer feels familiar to InfoPath builders, with a designer that maps cleanly to InfoPath patterns. NITRO Studio was specifically built with InfoPath users in mind, making the transition as straightforward as possible from a UI/UX perspective. The workflow layer maps to the kind of approval logic InfoPath designers were already wiring into SharePoint Designer.

That overlap shortens the rebuild. Teams that built or maintain the original InfoPath deployments can rebuild them in NITRO Studio without learning a new authoring paradigm. This is the practical reason Crow Canyon’s InfoPath migrations land faster than parallel migrations to Power Platform, where forms move into Power Apps, workflow moves into Power Automate, and the SharePoint data model often shifts into Dataverse.

Deployment options for NITRO Studio

NITRO Studio runs in any major Microsoft 365 and SharePoint environment. For organizations whose InfoPath deployment is in one environment, NITRO Studio fits there. For organizations whose InfoPath deployment is in more than one environment, NITRO Studio is installed separately in each environment, but Crow Canyon delivers all the installations as one coordinated migration, so the project does not split across two products. Here are the deployment options:

• SharePoint On-Premises (SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition), available in two modes:
  • Normal Mode, where the on-premises NITRO Studio installation connects to Crow Canyon’s Azure.
  • NITRO Secure (air-gapped) is a fully disconnected, high-security mode with no external communication, designed for organizations with stringent security requirements, including defense, intelligence, space, and nuclear operations.
• SharePoint Online within the customer’s Microsoft 365 tenant, with the NITRO Studio Engine hosted in one of four locations:
  • NITRO Studio Engine is hosted in Crow Canyon’s Azure environment (Shared).
  • NITRO Studio Engine is hosted in the customer’s own commercial Azure tenancy (Dedicated).
  • NITRO Studio Engine is hosted within the customer’s Microsoft Government Community Cloud (GCC) environment, enabling customers in regulated industries, as well as U.S. federal, state, and local government agencies, to maintain full control over both their data and software.
  • NITRO Studio Engine is hosted within the customer’s Microsoft GCC High environment, enabling organizations handling Controlled Unclassified Information (CUI) and ITAR-regulated data to maintain full control over both their data and software while meeting stringent security and compliance requirements. This option is particularly suited for highly regulated industries, defense organizations, and government agencies.

For GCC and GCC High deployments, NITRO Studio runs inside the customer’s own Microsoft government tenant, not on infrastructure managed or hosted by Crow Canyon. Your data and software stay where your compliance mandate requires them to.

What InfoPath did, and what NITRO Studio adds

What Happens to Existing InfoPath Forms and Data After Retirement?

Existing .xsn form templates and .xml form data files remain in SharePoint document libraries. They are not automatically deleted. What changed is how you get to them.

Before July 14, 2026, InfoPath templates and data could be downloaded from SharePoint libraries through the SharePoint Admin Center. Those Admin Center options were removed on the retirement date. Post-retirement, the remaining access path for opening either file type is InfoPath 2013 running locally on a workstation that still has the client installed, with file permissions to the source library. That workstation dependency is fragile and gets more fragile over time as new device images stop shipping Office 2013-era components.

For organizations still holding InfoPath artifacts as part of a retention or audit requirement, the practical approach is to extract the data into a supported format (CSV, structured storage, or a modern forms platform) while a working InfoPath 2013 install still exists somewhere in the environment. Waiting turns a routine export into a forensic exercise.

InfoPath Migration Examples: Air Wisconsin and Honu Services

Air Wisconsin: 400+ InfoPath forms replaced with NITRO Studio

Air Wisconsin’s business processes were highly dependent on Microsoft InfoPath, SharePoint Workflows, and other legacy systems. The challenge was scale. More than 400 InfoPath forms supported airline operations and back-office processes. The team needed a replacement that could match the existing functionality, reproduce it inside their Microsoft environment, and survive the InfoPath retirement without disrupting day-to-day operations.

Air Wisconsin moved to NITRO Studio. The migration covered both the InfoPath forms layer and the SharePoint Workflows underneath. The team rebuilt the deployments on a platform that runs natively inside SharePoint and uses the same list, library, and permission constructs Air Wisconsin’s developers were already familiar with.

Read the full case study: Air Wisconsin InfoPath Replacement Options.

Honu Services: from InfoPath to NITRO Studio across a dozen client environments

Honu Services, based in Hawai’i, provides business expertise, back-office support, and strategic development to more than a dozen small businesses and government agencies on the islands. The team needed a SharePoint-based forms and workflow solution that was dynamic, responsive, and easy to use across multiple client environments. The replacement had to reproduce applications across different clients and allow quick creation of forms without coding.

After moving from InfoPath to NITRO Studio, the team’s verdict was direct.

“NITRO Forms is far superior to InfoPath, and provides more functionality paired with great responsive technology. The limitations of InfoPath and lack of support prompted us to switch to NITRO Studio.”

Honu Services

Read the full case study: Honu Services NITRO Studio Review.

Which InfoPath Replacement Fits Your Environment?

Choose NITRO Studio if…

• Your environment is one or more of: SharePoint Online, SharePoint Server 2016, 2019, or Subscription Edition, your Microsoft GCC, your Microsoft GCC High, or air-gapped on-premises via NITRO Secure (even just one of these environments is a great fit)
• You are in Government, Healthcare, Banking, or another industry where security matters
• Your InfoPath deployment is large or paired with SharePoint Designer workflows
• You want flat, predictable pricing instead of per-form, per-flow, per-process, or per-connector meters
• You want forms, workflows, portals, dashboards, and the option to add purpose-built business applications (Help Desk, Purchasing, HR, Asset Management, Work Orders, and more)

Choose Microsoft Power Platform if…

• Your environment is cloud-only on Microsoft 365
• You have developer support for Power Fx, Dataverse, and connectors
• Your InfoPath scope was narrow, and the rebuild is small
• You have headroom in the Microsoft license bill for approximately $42,000 per year per 100 users

Choose FlowForma if…

• Your environment is cloud-only
• You have a budget of roughly $30,000 or more per year (about five times the cost of NITRO Studio’s flat-rate license)
• You have a small, well-defined set of processes (under 30), and the process count will not grow much
• You do not need SharePoint on-premises, GCC, GCC High, or air-gapped deployment
• Process governance and audit features are the dominant requirements

Choose Plumsail Forms if…

• Your scope is forms-only and will stay that way
• Your environment is SharePoint Online, SharePoint Server 2019, or Subscription Edition (not 2016)
• You have SharePoint developer skills in JavaScript and CSS
• You are comfortable assembling the workflow, portal, and dashboard layers from other tools
• You can budget separately for Power Automate or another workflow product to handle automation, since Plumsail Forms by itself does not replace InfoPath’s workflow side

Why Organizations Choose Crow Canyon for InfoPath Migration

Crow Canyon Software, Headquartered in California, has been a Microsoft Preferred Partner for 27+ years. The InfoPath replacement work is not a new offering. It is the work the company has been doing since InfoPath was first deprecated in 2014. Over a thousand organizations run on NITRO Studio today, with strong adoption in Government, Healthcare, and Banking, the three most highly regulated industries, where data residency, compliance, and platform security are non-negotiable.

The trust signal list spans US federal agencies, state agencies, large enterprises, healthcare systems, financial institutions, airlines, higher education, non-profits, space agencies, and power plants. Specific customers include the State of California Franchise Tax Board, US Department of Justice, Office of Naval Intelligence, US Equal Employment Opportunities Commission, California Air Resources Board, Renton Regional Fire Authority, Ballad Health, IDT Biologika GmbH, FSU Credit Union, Air Wisconsin, Ventura Foods, Ingram, AstenJohnson, National University of Singapore, and University of Houston.

Three things make the Crow Canyon InfoPath engagement different from a typical platform purchase:

• A structured migration approach, delivered through Crow Canyon’s professional services, that tracks form inventory, conversion status, and cutover progress throughout the project.
• A dedicated migration team that runs the rebuild as a managed engagement when the customer prefers turnkey delivery, or works alongside the customer’s internal team in a hybrid model.
• Support for SharePoint On-Premises (connected or air-gapped via NITRO Secure) and SharePoint Online / Microsoft 365 (with the NITRO Studio Engine hosted in Crow Canyon’s Azure (Shared), your own commercial Azure (Dedicated), your Microsoft GCC, or your Microsoft GCC High) under one platform, so organizations with mixed cloud and on-premises deployments do not split the migration across two products, and organizations using a single environment get the same platform built for any of them.

Pricing starts at $5,988 per 100 users per year for the NITRO Studio license, with unlimited forms and unlimited workflows. There are no usage overages or surprise fees. The license price stays stable through the year. Professional migration services are quoted separately based on the scope of your deployment.