1C:UPP support is ending: what manufacturing company executives should do

If your company still runs on 1C:Manufacturing Enterprise Management (1C:UPP), you will soon have to make a decision — whether you are ready for it or not. 1C is winding down support for this configuration: updates reflecting changes in legislation stop coming out, statutory reports are no longer updated, and every new customization becomes more expensive and riskier. The system may keep “working” — on the surface, nothing will change. The real problem is different: it stops being manageable. Let’s look step by step at what the end of support actually means, why the “if it isn’t broken, don’t touch it” strategy does not work here, and what options you really have.

What “end of support” means in practice

On paper, 1C:UPP will still start up and process routine transactions. But technical support is not an abstract formality — it is several specific things that stop working one after another:

• Changes in accounting and tax legislation no longer make it into the configuration automatically — they will have to be added through custom development at extra cost, if you can find anyone to do it at all.
• Sooner or later, statutory reports will no longer match the current forms — and the risk of errors in reports to the tax authorities falls on the chief accountant, not on the system.
• The pool of specialists willing to support 1C:UPP will only shrink — 1C is training new partners for 1C:ERP, not for a discontinued system, and in 2–3 years, finding an experienced 1C:UPP specialist will be noticeably harder and more expensive.
• Any customization or integration with new equipment, a bank, or a marketplace is done “at your own risk” — with no vendor guarantees and no ready-made solutions to rely on.

A particular danger is that none of these problems appear all at once. They build up gradually, and the typical scenario goes like this: first, “we’ll customize what we need in-house,” then “we’ll hire a freelancer who still remembers 1C:UPP,” and a year or two later — an emergency migration on a tight deadline, because at some point the system can no longer handle the business’s day-to-day needs, and there is no time left to combine daily operations with a full-scale ERP implementation project.

Why “waiting a little longer” is not a free strategy

Postponing the migration often seems like the safest choice: the system works, so there is no pressing problem. In reality, the cost of waiting grows quietly but steadily. First, the longer a company runs on an unsupported system, the more “patches” and non-standard customizations pile up in it, and all of them will have to be untangled during data migration — which directly increases the cost and duration of the future migration. Second, 1C:UPP specialists are becoming a scarce and expensive resource: the labor market is already shifting toward 1C:ERP, and in a year or two the migration will most likely have to be done on a tighter schedule and at a higher price than today. Third, postponing the migration means the company keeps missing out, year after year, on the very things that make moving to a modern system worthwhile: accurate costing, real-time management reporting, and proper production planning. In other words, it is not only a risk but also a lost opportunity.

Options for businesses running 1C:UPP

Before talking about migrating to 1C:ERP, it is worth taking an honest look at all the options — in practice, there are three. The first is to leave everything as it is and support the system in-house or with an outside specialist. This is the cheapest option in the short term, but it is precisely the one that carries the risks described above: no vendor guarantees, rising costs for every customization, and no new functionality to meet changing business needs. The second is to move to a smaller-scale 1C product (for example, a customized 1C:Accounting 8 or 1C:Small Business Management) if production is not a critical area for the company. This path suits small companies, but for a business with full-scale manufacturing, it usually means losing functionality that 1C:UPP already had — planning, dispatching, and cost accounting by process stage. The third is to move to 1C:ERP, the direct successor to 1C:UPP in terms of system design. For most manufacturing companies with revenue of several hundred million rubles or more, this is the most logical path: the system is conceptually familiar to your team, and the scope of functionality is not only preserved but expanded — thanks to up-to-date production and management modules that 1C:UPP has long been missing.

How the migration works, in brief

Executives do not need to understand the technical details of the migration — that is what the systems integrator is for. But it helps to understand the overall logic, so you can evaluate contractors’ proposals and not be afraid of the process itself. The migration starts with a business analysis: the integrator examines how your processes and customizations are set up in your current 1C:UPP and decides what is carried over “as is,” what needs adapting, and what should have been dropped long ago as legacy clutter. Next, data and settings are migrated to 1C:ERP, and the system is fine-tuned to your processes — without replicating all the old customizations, which in itself reduces both the cost and the duration of the migration. The project ends with pilot operation: for a while, both systems can run in parallel to make sure the new reports and calculations match the old ones before 1C:UPP is switched off completely. The key mistake companies make in this kind of migration is trying to move absolutely everything to the new system, including customizations layered on over the years. A good integrator first helps you figure out which parts of your current accounting logic the business actually needs today and which are simply historical baggage that there is no point in carrying forward.

What to do right now

Even if you do not plan to migrate to 1C:ERP in the coming months, it makes sense to understand the scale of the task in advance: how many non-standard customizations your current 1C:UPP has, which processes depend on outdated logic, and how much time the migration will realistically take for your particular company. You can find this out with a free audit of your current system — with no obligation and no disruption to your operations. If you are ready to discuss the migration in concrete terms, take a look at our service “Turnkey migration from 1C:UPP to 1C:ERP”: what is included, how the project runs, and how long it takes. We have already carried out such migrations for manufacturing companies and are ready to look at your specific situation — request demo access or an audit on our website, and we will show you how it would look for your company.