Kudzu Software

News: Lightning Tools Announces Tentative Agreement to Acquire Kudzu Software Inc. Assets We’re thrilled to announce that Lightning Tools has reached a tentative agreement to acquire the intellectual property of Kudzu Software Inc. This strategic move enhances our capabilities in delivering top-tier solutions for Microsoft 365, empowering businesses with even more robust tools for collaboration, automation, and data management. ?? Read the full announcement: https://lnkd.in/e9K9ngNK Stay tuned for more details on what this means for our customers and partners! #LightningTools #Microsoft365 #Innovation #Acquisition #Kudzu #InfoPath

After today, there's only one more Halloween before July 14th, 2026.?With that in mind I asked Grok: "It's Halloween 2024 and you find yourself with 1000's of Microsoft InfoPath form templates and data that need to be converted before July 14, 2026.?Can you think of some things that would be more terrifying than trying to convert all of that without the help of Kudzu Software?" Grok: Ah, you're in a pickle, aren't you? Here are some scenarios that might give even the task of converting thousands of InfoPath forms a run for its money in the terrifying stakes: 1.?Being stuck in an endless loop of a '90s screensaver - Imagine, instead of dealing with form conversion, you're trapped in a room where the only thing on the screen is that flying Windows logo or the mesmerizing maze. Forever. 2.?An AI that only communicates through dad jokes - Every time you ask it to convert a form, you get responses like, "Why did the InfoPath form go to therapy? Because it had an identity crisis with all its fields!" 3.?A world where every meeting is a PowerPoint Karaoke - Instead of data conversion, you're forced to present random slideshows with spontaneous narration. Your audience? A room full of judgmental cats. 4.?Internet Explorer becomes the only browser again - You're back to the days of waiting minutes for a page to load, but this time, it's your life on the line with every form submission. 5.?All your coffee turns into decaf - The horror of facing the InfoPath conversion without the sweet nectar of caffeine to keep your sanity intact. 6.?Your spellchecker decides to only work in reverse - Every word you type correctly gets swapped for something hilariously wrong, like "InfoPath" turning into "InFoPaTh." 7.?Your computer only accepts inputs in binary - Wanna convert a form? Better start thinking in ones and zeros, and hope you remember your binary. 8.?Every time you successfully convert a form, a new form appears - It's like the mythical Hydra, but instead of heads, it's forms. Convert one, and two more pop up in its place. 9.?You're tasked with teaching a class of toddlers how to use Microsoft Office - Imagine explaining the concept of form conversion to beings who think Ctrl+Alt+Del is a fun game button. 10.?The only tool available for conversion is a physical abacus - Good luck translating your digital forms into beads and wires. Honestly, converting thousands of InfoPath forms might just be a walk in the park compared to these spine-chilling alternatives. Happy Halloween, indeed! #HappyHalloween #SharePoint #InfoPathReplacement #SharePointForms #PowerApps

#ReplaceInfoPath and #ReplaceNintex PSA: if you think you have or know you have InfoPath and/or Nintex for SharePoint forms in your on-prem or M365 SharePoint environments you should make sure you take a proper inventory. The following are all FREE: Microsoft provides a tool for InfoPath: https://lnkd.in/gjkHDcG6 Nintex has tools/scripts you can run, but I'm not aware of a place you can download them directly, so contact someone from your account team. Kudzu Software has a tool that can find both while also analyzing the forms for complexity and portability: https://lnkd.in/genhiDdM It's worth noting that we rarely encounter a prospective customer that is certain what forms they have and/or how many they have. Recently, we had one prospective customer approach us about replacing Nintex, thought they had around 500 forms, and ended up having 557...which was not too bad of a guess on their part. What shocked them is the FORMulator also found 1,261 InfoPath forms with over 500 of them still in use (...filled out in the last 12 months). The problem with InfoPath in particular is it has been around for two decades and in many cases the people responsible for building these forms have left. And then you have the double whammy when they don't have anyone on staff with knowledge of the platform "I didn't know these existed and don't know what they are" is not what you want to be left saying on July 15th, 2026. Act now! #TheMoreYouKnow #SharePoint #SharePointOnline #SharePointForms

#TrueStoryTuesday #ReplaceInfoPath and #ReplaceNintex conversation today with a prospective customer after a Kudzu Software demo and some Q&A. Customer: this is really slick, but my team thinks they can convert our InfoPath and Nintex for SharePoint forms to Power Apps by hand. Me: they absolutely can, so it's really a question of having enough time and resources to do it...and, as necessary, knowing how to convert the data and making sure the end result keeps your business compliant. Customer: what do you mean by "convert the data and keep compliant"? Me: the FORMulator says you have a few hundred InfoPath forms deployed to form libraries and another hundred Nintex forms with repeaters. The form libraries are just a bunch of XML documents that will need to be converted to items in one or SharePoint lists or rows in one or more Dataverse tables. The Nintex forms with repeaters will have one or more XML fragments stored in hidden fields that will need to be extracted and written out to child SharePoint lists or Dataverse tables. Me (cont'd): And then you have to make sure anything you do meets your highly-regulated org's records management/retention policies, meaning do you need to maintain a digital record, beyond just the data, of all those filled out forms? Put more simply, imagine getting a records request from legal or compliance and all you have to give them is an XML document. Customer: silence. Me (after waiting 15-20 secs): I mean your team can do all that by hand or write some scripts or crack open a code window like we did, but you're in for a bumpy ride. Customer: you gave us a lot to think about, let us discuss internally and get back to you: Customer (less than an hour later): can we schedule another session to discuss next steps? Me: ?? #SharePoint #PowerApps #SharePointForms #InfoPath