Moving from 1C/BAS changes how accounting is performed; it is not simply a database copy. Identically named documents in different products may follow different posting rules. For the accounting team to explain every amount after launch, define the cutover date, migration scope and reconciliation method beforehand.
Why migrating the entire history is not always worthwhile
Historical postings may depend on old configuration and customisations. We first compare requirements: daily work with open orders, analysis of past sales and access to original documents. For each, decide whether the new system needs records, a separate archive or a report.
The archive must remain readable by authorised staff. Before changing servers, check the backup, access licensing and the ability to retrieve required documents. Your accountant or specialist adviser determines retention periods and legal obligations for your circumstances.
Clean reference data before import
Two counterparties with different spellings may be the same company. Conversely, similarly named products may use different units. We agree stable mapping identifiers and check duplicates, rates, currencies, warehouses and contracts. Keep the original export separate from the corrected version.
For example, a pack and an individual item must not become one product without a conversion rule. Otherwise the report quantity may look plausible while stock is wrong. The accounting data owner decides the mapping; the integrator implements it.
How to reconcile balances and open documents
Choose a control date and record balances in both systems. Compare dimensions as well as totals: account, counterparty, contract, warehouse, product and currency. Even a rounding difference needs an explanation rather than a concealed manual adjustment.
Separately check unfinished activity: advances, outstanding debts, reservations and partially fulfilled orders. A test receipt, sale, return and payment must correctly change migrated balances. These checks establish whether the database is operationally ready.
Cutover and the first operating period
Rehearse the migration on a copy. Record duration, errors and repeatable actions, then agree a window for stopping writes to the old system. Give the final export a clear version: accidentally mixing files from different dates invalidates reconciliation.
After launch, the accounting team checks agreed reports and typical operations. We record discrepancies, causes and corrections in the migration log. Readiness means a confirmed result and an accessible archive, rather than merely a successful import message.
Sources and further reading
