CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU

Moving from 1С/BAS to Oracle NetSuite

Move from 1С/BAS to NetSuite in stages: customers, suppliers, items, stock, open debts and sales history go across, and work goes on while both systems run in parallel

Companies that sell abroad or plan to often choose NetSuite instead of 1С/BAS: one cloud system for sales, stock and finance, reachable from anywhere. 1С/BAS is also on the official prohibited software list. What holds the move back is the data and the fear of stopping work. We move you in stages: first we look at what is really in 1С/BAS and clean it, then make a trial load, run both systems in parallel and reconcile with the accountant. 1С/BAS is switched off only after the figures match. Below: what we carry over, how the move goes and which capabilities of NetSuite we rely on.

What we move

  • 1С/BAS → Oracle NetSuiteCounterparties from 1С/BAS — companies and individuals with tax code, addresses, contact people and bank details — become customer and vendor records in NetSuite; duplicates are merged before the load.
  • 1С/BAS → Oracle NetSuiteItems with units, groups, barcodes and the price types you really use become NetSuite items with their prices.
  • 1С/BAS → Oracle NetSuiteExtra details you added to client and product cards in 1С/BAS yourselves move into your own fields in NetSuite, so nothing is lost on the way.
  • 1С/BAS → Oracle NetSuiteStock balances by warehouse on the switch-over date are loaded as opening quantities, so the warehouse in NetSuite starts from the same numbers.
  • 1С/BAS → Oracle NetSuiteUnpaid customer invoices and debts to suppliers on the same date move as open balances, so collections go on without a gap.
  • 1С/BAS → Oracle NetSuitePast orders and invoices for the period you choose are carried over as sales history, so every client card shows what was bought before.

How the move goes

  • In NetSuite your administrator creates a separate role for the exchange with access by keys, not by an employee's login and password.
  • 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 NetSuite 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 NetSuite, 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 NetSuite, 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 NetSuite 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

01

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 NetSuite the client has one card with the whole debt.

02

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.

03

History left behind

Before in the new system the salesperson cannot see what the client bought last season and asks the accountant to dig into 1С/BAS.

After the client's past sales are in NetSuite next to his card, and nobody needs to open 1С/BAS.

04

A load repeated twice

Before a connection drops halfway through a load, the load is started again, and half the clients appear twice.

After each record goes with its own unique key, and NetSuite does not create a second copy when the same record comes again.

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
  • Through that interface records can be created, read, updated and deleted, and custom records and fields are handled the same way as standard ones.

    Source: docs.oracle.com ↗ checked 2026-09-28
  • Long operations can run in the background: the request goes into a queue and the result is collected later, so a large history load does not block the connection.

    Source: docs.oracle.com ↗ checked 2026-09-28
  • NetSuite has built-in protection against duplicates: a repeated request with the same unique key does not create a second record.

    Source: docs.oracle.com ↗ checked 2026-09-28
  • Outside systems cannot sign in with an employee's login and password; access is by keys, and Oracle names its newer key method as the preferred one.

    Source: docs.oracle.com ↗ checked 2026-09-28

Limits

The limits come from both systems. A long sales history is loaded in the background in portions, so it takes time; while it runs, both systems stay in use. Access for the exchange is only by keys that your NetSuite administrator issues, so the administrator's help is needed at the start. Not every 1С/BAS document has a match in NetSuite: what does not fit stays in the 1С/BAS archive, and we agree the list at the audit. 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.

  1. 01

    Leave a request

    Describe the task in the form — in text or by voice. Budget and timing are optional.

  2. 02

    We review and estimate

    A developer studies the brief, asks about anything unclear and sends an estimate.

  3. 03

    We start

    Once scope and price are agreed, the work begins.

or write to info@coreviaflow.space

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 NetSuite, 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 NetSuite. The full 1С/BAS database is kept as an archive, so an old document can still be found for an audit or a dispute.

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.