Moving from 1С/BAS to SAP

Move from 1С/BAS to SAP in stages: customers, suppliers, products, stock and open debts are cleaned and loaded, while 1С/BAS keeps running until the figures match

When a company grows out of 1С/BAS, SAP is often the next step: finance, supply chain and sales in one system. 1С/BAS is also on the official prohibited software list, which makes the decision easier. The hard part is the data: years of 1С/BAS hold duplicate clients, old items and debts nobody remembers. We take that part: we look at what is really in 1С/BAS, clean it, make a trial load, and keep both systems in parallel until the reconciliation matches. The SAP side is usually run by your own team or integrator, and we agree the loading with them. Below: what we carry over, how the move goes and which capabilities of SAP we rely on.

Request an integration System page: 1С/BAS →System page: SAP →

What we move

1С/BAS → SAPCounterparties from 1С/BAS — companies and individuals with tax code, addresses, contact people and bank details — become customer and supplier records in SAP; duplicates are merged before the load.
1С/BAS → SAPItems with units, groups and barcodes become product records in SAP, in the structure your SAP team has set up.
1С/BAS → SAPThe price types you really use in 1С/BAS are carried over as sales prices in the form agreed with your SAP team.
1С/BAS → SAPStock balances by warehouse on the switch-over date are loaded as opening stock, so the warehouse starts in SAP from the same numbers.
1С/BAS → SAPUnpaid customer invoices and debts to suppliers on the same date move as open items, so collections and payments continue without a gap.
1С/BAS → SAPSales history for the period you choose is carried over for reference and reports; older years stay in the 1С/BAS archive.

How the move goes

We meet the team that runs your SAP and agree how the data is received: through SAP's own ready data-exchange tools or in the format they load themselves.
We look at what is really in your 1С/BAS: which catalogues and documents are in use, what is outdated, where data is kept in unusual places; together we decide what moves to SAP and what stays in the archive.
Before the move we clean the data: merge duplicate counterparties and items, fix tax codes and units, and mark old records the new system does not need.
We make a trial load into a test copy of SAP, and your people check customers, products and balances on familiar examples before anything touches the working system.
For the transition both systems run in parallel: new work is done in SAP, and 1С/BAS stays at hand as a reference, so shipments and payments do not stop.
We reconcile together with your accountant: balances, debts and stock in SAP against 1С/BAS on the same date; every difference is explained before the next step.
Only after the reconciliation is 1С/BAS switched off for daily work; its database is kept as an archive for audits and old questions.

Automation scenarios

One client, several cards

Before the same client sits in 1С/BAS under several spellings, and his debt is split between the cards.

After duplicates are merged before the move, and in SAP the client has one card with the whole debt.

Afraid to switch

Before the move is postponed again and again, because nobody knows how the warehouse will ship on the day of the switch.

After balances are loaded on an agreed date, both systems run side by side, and shipping goes on as usual.

Who still owes

Before after a move nobody is sure which invoices were paid before it, and reminders go to clients who have already paid.

After open debts are moved on one date and reconciled with the accountant, so reminders go only to those who really owe.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

BAS products are on Ukraine's official list of prohibited software (Cabinet resolution №1335 of 22.10.2025, based on Presidential Decree №601/2024 of 02.09.2024). The direct ban applies to the state sector, critical infrastructure and systems processing state information resources.
Source: impactalaw.com ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
S/4HANA Cloud is open and extensible: it ships with ready-to-go APIs, tools and documentation for integrating with other systems.
Source: www.sap.com ↗ checked 2026-09-28
SAP Business Accelerator Hub (api.sap.com) is the official catalogue where SAP's APIs, including S/4HANA, can be discovered and tested; there are REST, OData and SOAP APIs.
Source: developers.sap.com ↗ checked 2026-09-28
SAP Integration Suite is SAP's integration platform (iPaaS) that connects SAP and third-party applications such as Salesforce, Workday, AWS and ServiceNow.
Source: www.sap.com ↗ checked 2026-09-28

Limits

The limits come from both systems. SAP is usually set up by your own team or integrator, and the structure of data on the SAP side is theirs to decide; we prepare and load data under their rules. Which ready exchange tools are available depends on your SAP edition and setup, and we check this at the start. Accounting history from 1С/BAS rarely fits SAP one to one, so older periods usually stay in the 1С/BAS archive rather than being rebuilt. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Is it legal to stay on 1С/BAS?

1С/BAS is on the official prohibited software list. The direct ban covers the state sector, critical infrastructure and systems with state data. For a private business it is formally allowed but considered a risk — check with your lawyer.

Will work stop during the move?

No. For the transition both systems run in parallel: new documents go into SAP, and 1С/BAS stays as a reference until the reconciliation shows the same figures. 1С/BAS is switched off only after that.

What happens to the history and the archive?

The history you need every day — what each client bought, who owes what — moves to SAP. The full 1С/BAS database is kept as an archive, so an old document can still be found for an audit or a dispute.

We already have an SAP integrator. What is your part?

The 1С/BAS side: we export the data, clean duplicates, check it with your people and hand it over ready for loading, or load it ourselves by the rules agreed with the integrator. The SAP setup itself stays with them.

Tell us what needs to be connected

Describe the task in text or a voice message. We look at your setup and reply with a plan.

Request an integration

What you can order

Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.

CRM implementation

Choose the system, set up the pipeline, migrate data, train the team.

Learn more →

CRM integration

Accounting, telephony, website, payments and messengers feed the CRM on their own.

Learn more →

Telegram chatbots for business

Orders, requests and answers around the clock, straight into your CRM.

Learn more →

n8n and Make automation

Flows between CRM, email, spreadsheets, payments and AI, on your own server.

Learn more →

What you can order from CoreviaFlow →

Each system on its own

Accounting & ERPUA

1С/BAS

Already running your accounting in 1С/BAS? We automate the work around it

See scenarios →

Accounting & ERPEU

SAP

An order confirmed in the CRM becomes a sales order in SAP, the invoice and the payment from SAP show up on the client's card, and the customer list stays the same in both systems without retyping.

See scenarios →