Summer is long gone, and yet nothing has happened \u2013 that\u2019s exactly the treacherous feeling. Meanwhile, three rounds of security patches have been released by Microsoft, and your server is just filling up with dust. And then there\u2019s autumn, the time when companies and cities plan their budgets for the next year. To solve it after the first incident? Nonsens.<\/strong>\u00a0<\/p>\n\n\n\n Because \u201eIt works\u201c<\/em> a \u201eIt\u2019s okay\u201c<\/em> It\u2019s not the same. The end of support means that every new security hole that appears in the old SharePoint will remain open forever. No one will fix it or patch it up anymore.<\/strong> Not today, not in a month, and not even in a year.\u00a0<\/p>\n\n\n\n And on SharePoint, you usually don't have unnecessary documents stored. There are contracts, data about clients and employees, invoices, and internal policies. Explaining to the auditor, the insurance company, or the management that this is the whole thing runs on a system for which no one is responsible anymore<\/strong>, <\/strong>Consultation is not exactly popular. For the authorities that manage citizens' data, this applies multiple times. <\/p>\n\n\n\n Almost. For those who want to stay in their own, Microsoft has a successor. It is called SharePoint Server Subscription Edition and, unlike the old versions, it has no end date. If you update it properly, it will serve continuously.<\/strong> You can access it directly from SharePoint 2016 and 2019, without having to go through other versions.\u00a0<\/p>\n\n\n\n But there is one snag. Not even there InfoPath forms do not have support<\/a>. They are gone for good. And in the cloud, Microsoft is turning them off too. So whatever you decide, The forms must be modified. <\/strong>A surprise that no one ordered, but that will appear in every package. <\/p>\n\n\n\n A private server is like your personal car. It is yours and you can do whatever you want with it. But someone has to fill it with fuel, service it, wash it, and occasionally replace it with a new one. It makes sense especially if: <\/p>\n\n\n\n Cloud, i.e. SharePoint in Microsoft 365, is more like a car leased for a period of time. You drive on the current model and the provider takes care of servicing, maintenance, and technical updates. You don\u2019t have to maintain your own servers or worry about which version to upgrade to in a few years because you always use the current one. It makes sense especially when you\u2019re already You pay for the Microsoft 365 license<\/strong>, But you only use outlook and the office applications from them. But if you want them to work together, you need to install the Office apps. Their colleagues also received the document <\/strong>on the road, from home or in the field, and you don't have the time or people to manage your own servers. And if you plan to help with AI<\/strong>, Cloud is a clear choice, because the news, including Copilot, comes first here.\u00a0<\/p>\n\n\n\n Just be careful; moving to the cloud is not just a simple transition from an old car to a new one. <\/strong>Rather, it resembles a comprehensive inspection before the next trip: some components are no longer compatible with the new model, for example the older automatic workflows in Microsoft Cloud. discontinued in April 2026<\/a>. So expect that some of the equipment will need to be repaired, replaced, or left in the garage during the migration. And as with any thorough inspection, here too you\u2019ll find something that no one ever thought you still carried in the trunk.\u00a0<\/p>\n\n\n\n Vacation request. Material order. Car reservation. Invoice approval. Once upon a time, someone drew them in InfoPath or the old Nintex, then they left the company and since then no one dared to open them. Now is the time. The good news is that there is enough spare time:\u00a0<\/p>\n\n\n\n And an even better report at the end. With such cleaning, it usually turns out that some forms have not been used for years and others can be combined into one. Less forms, less clicking, less nonsense.<\/strong> <\/p>\n\n\n\n A few examples from our practice where we put the agenda in a proper place in Microsoft 365 in Opium.systems: <\/p>\n\n\n\n Exactly such agendas still live in old InfoPath or Nintex forms in many companies and offices today, waiting for someone to liberate them. <\/p>\n\n\n\n You don't have to solve everything at once. Just four steps are enough: <\/p>\n\n\n\nAfter all, it works. Why should we worry about it?<\/strong><\/h3>\n\n\n\n
![\"The](\"https:\/\/opiumsystems.sk\/wp-content\/uploads\/2026\/10\/stary-sharpoint-novy-sharepoint-1024x683.png\")
<\/figure>\n\n\n\nWe'll buy a new server and that's sorted, right? <\/strong><\/h3>\n\n\n\n
Your own server or the cloud? <\/strong><\/h3>\n\n\n\n
\n
![\"The](\"https:\/\/opiumsystems.sk\/wp-content\/uploads\/2026\/10\/cloud-vs-server-1024x1024.png\")
<\/figure>\n\n\n\nAnd what about those forms? <\/strong><\/h3>\n\n\n\n
\n
What does it look like when it works? <\/strong><\/h3>\n\n\n\n
\n
Where to start?<\/strong> <\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/opiumsystems.sk\/wp-content\/uploads\/2026\/10\/stary-sharpoint-infografika.png\")
<\/figure>\n\n\n\n