Is your business ready for new requirements  2026 and risks of using 1C/BAS

Businesses face new risks in 2026

• —Cyberattacks and risks of old systems
• —chaos between Excel, CRM and 1C/BAS
• —"A "zoo" of services and manual processes
• —lack of a unified picture of the business
• —the complexity of scaling and international work

Alexey Bardakov

CEO of ToDo - 22+ years in building ERP systems

CEO - TODOKYIV / DUBLIN

• 01ERP and digital business transformation
• 02Automation of production, distribution and service business
• 03Building managed business processes
• 04Scaling companies through modern ERP systems

22+ years of experience in ERP and automation 35+ of ERP projects implemented

What will we talk about

1. 01 Why businesses refuse from 1C/BAS 15:00

   The government ban on 1C/BAS has forced Ukrainian companies to take notice of a problem that IT specialists have been discussing for years. 1C is a monolithic system that tries to do everything at once, but the results are usually mediocre across the board. The modern approach is a stack of two or three specialized systems, each of which excels at its own specific task. Let’s explore why the solution for 2026 isn’t about finding a «new 1C,» but rather about building a stack tailored to your business’s specific processes.

2. 02 Risks of old ERP systems in 2026 15:10

   Any ERP system developed using the 1990s paradigm poses real technical risks today: outdated architecture, a lack of native cloud integration, and weak data security. If you’re using 1C version 8.2 or earlier, this system no longer communicates with modern marketplaces, mobile apps, or payment services. Let’s break it down specifically: which systems will become technical debt tomorrow, and what to do about it.

3. 03 Cyber warfare and new security requirements 15:25

   After 2022, any software of Russian origin poses a direct security risk, regardless of whether it has been customized or localized. The State Special Communications Service registry and the NBU’s letter on zero tolerance are creating regulatory pressure that will only intensify. Let’s discuss not only the legal implications but also the practical question: how to choose an ERP system that meets the new security and data storage requirements amid active cyberwarfare.

4. 04 How a «zoo» of systems destroys controllability 15:40

   The temptation to replace a single system with five specialized ones often leads to worse results—data duplication, gaps between systems, and a lack of process transparency. The correct stack architecture does not call for «everything separate»: the optimal solution for a medium-sized business is 2–3 systems with clearly defined areas of responsibility and API integration between them. Let’s look at how to plan the architecture from day one so you don’t have to fix it two years down the road with costly reworks.

5. 05 How to switch to a new ERP without chaos 15:55

   A typical migration project from 1C takes between 3 and 9 months, depending on the size of the company and the number of customizations. The most costly mistakes are an unprepared accounting department, unprocessed data, and the failure to run both systems in parallel during the transition period. Let’s take a detailed look at a step-by-step checklist: what to do 30 days before the start, how to conduct a technical audit of the current 1C system, and how to properly create a transition timeline without rushing.

6. 06 Case studies of Ukrainian companies 16:15

   Real-world case studies from companies that have already completed the migration: a retail chain with 100 employees that migrated to Odoo + MASTER in 4 months, a manufacturing company with 300+ employees that migrated to IT-Enterprise, and an IT company with international operations that migrated to SAP. Each case study details the specific challenges that arose, the solutions that worked, and the numbers: how much it cost, how long it took, and what results were achieved.

7. 07 Q&A session 16:35

   Honest answers to your questions about choosing an ERP system, TCO, the impact on your team, and industry-specific recommendations. We’ll answer honestly, including questions that may seem sensitive but are critical: «Can we wait another year?» and «Exactly how much will this cost us?» If you don’t have time to ask live, leave your questions in the chat—we’ll answer them after the webinar.

Webinar participants will receive

Four practical materials that will help you start the transition to a new ERP next week.