1C and BAS migration

Move accounting data from 1C and BAS

We migrate accounting history, balances and essential customisations into your chosen platform with parallel operation and controlled reconciliation.

Discuss your project
01

Why Ukrainian organisations are planning a move

1C and BAS appear on Ukraine’s restricted-software list created under Cabinet of Ministers Resolution No. 1335 of 22 October 2025 and related sanctions decisions. There is no direct administrative fine for ordinary private-business use. The practical issues are continuity of updates and support, eligibility in public-sector and critical-infrastructure contexts, limited integration with modern analytics and AI, and trust expectations from partners. We compare target platforms neutrally, including MASTER, Odoo, BAF, SAP Business One, Microsoft Dynamics, ISpro and Ukrainian cloud accounting products.

  • Accounting-process and dependency map
  • Vendor-neutral platform comparison
  • History and document retention plan
  • Completeness criteria and reconciliation rules
02

What is migrated

Scope can include reference data, opening and current balances, transaction history, primary documents, relationships, custom reports and business-specific extensions. We also define what will not be moved: duplicates, technical records, obsolete reference data or logic that the target platform handles differently. Every exclusion has a reason and an agreed archive-access method. This prevents a common mismatch between an expected full replica and a delivery containing only current balances.

03

Parallel operation and reconciliation

The old and new systems run in parallel until control totals and selected processes are confirmed. Your team reconciles balances, turnover, documents, reports and representative transactions using agreed rules. Differences return to the transformation process rather than being silently corrected by hand. At acceptance, we hand over the data model, conversion rules and integration documentation. These assets also provide a cleaner foundation for analytics and later AI use cases.

Fit before scope

Is this the right starting point?

Use these criteria for an initial orientation. The final recommendation follows a review of your context, data and constraints.

A good fit when

  • Software is restricted, unsupported or creates operational risk
  • Data, history and integrations must be preserved
  • Process and acceptance owners are available

Resolve this first when

  • Only licence procurement is required without dependency analysis
  • A target was selected without validating processes and data
  • No one owns reconciliation and the cutover decision

Answer first

How should you choose a replacement?

A safe replacement of 1C or BAS starts with an inventory of accounting environments, customisations, integrations and reporting—not with selecting a new product. The target platform is chosen after financial, management and statutory accounting requirements are recorded.

01

Process fit

Required accounting models, source documents, approvals and statutory reporting are supported.

02

History transfer

Reference data, balances, open transactions and the agreed history depth can be migrated.

03

Solution control

Documented integrations, roles, audit trails, backups and the ability to change providers.

Evidence of completion: Completeness is demonstrated through turnover and balance reconciliation, control documents and an agreed parallel-run period.

Frequently asked questions

Frequently asked questions

How long does migration take?

The supplied project guidance ranges from three months for standard accounting to nine months for a highly customised configuration. Exact timing follows configuration discovery.

Are private companies fined for using 1C?

There is no direct fine for ordinary private-business use. Restrictions apply to public bodies, state enterprises and critical infrastructure; other organisations face operational and reputational considerations.

Can historical records remain accessible?

Yes. Discovery defines which history belongs in the live system and which records should remain in a controlled, searchable archive.

Ideas on this topic

AI data readiness: seven questions before the first pilotA single source of truth: what it means in practiceAPIs and integrations as a foundation for governed data exchange

Choose the right first step

Start with the decision you need to make

Each path produces a concrete next-step artefact rather than a generic technology presentation.

First step

Let's discuss your challenge.

We will clarify data availability, constraints and a realistic pilot format.