CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU

Moving from 1С/BAS to Microsoft Dynamics 365 Sales

Move the sales side from 1С/BAS to Microsoft Dynamics 365 Sales in stages: clients, contacts and open orders go across while the team keeps selling

Larger companies often keep clients and orders in 1С/BAS next to the books and want a proper sales system for the team; Microsoft Dynamics 365 Sales is a common choice. 1С/BAS is on the official prohibited software list, which makes the decision easier. Dynamics 365 exchanges data through an open standard, so loading does not depend on special Microsoft tools. We move the sales side in stages: we look at what is really in 1С/BAS, clean out duplicates, make a trial load and let both systems run side by side until the figures match. Dynamics 365 Sales is a CRM, so accounting and tax reporting go to a separate accounting program your accountant chooses. Below: what we carry over, how the move goes and which Dynamics 365 capabilities we rely on.

What we move

  • 1С/BAS → Microsoft Dynamics 365 SalesCounterparties from 1С/BAS — companies and individuals with tax code and addresses — become client records in Dynamics 365, in the structure your administrator has set up; duplicates are merged before the load.
  • 1С/BAS → Microsoft Dynamics 365 SalesContact people with phones and emails become contacts linked to their company, so the manager knows whom to call.
  • 1С/BAS → Microsoft Dynamics 365 SalesCustomer orders that are not yet closed become open sales in Dynamics 365, so they are finished there rather than in 1С/BAS.
  • 1С/BAS → Microsoft Dynamics 365 SalesPayments on those open orders move with them as information, so the manager sees what the client has already paid.
  • 1С/BAS → Microsoft Dynamics 365 SalesSales history by client for the period you choose is carried over as reference, so the manager sees what the client bought before.

How the move goes

  • With your Dynamics 365 administrator we agree which account the load runs under and where each 1С/BAS field goes: the licence of that account sets how many requests it may make a day.
  • We look at what is really in your 1С/BAS: which catalogues and documents sales use, what is outdated; together we decide what moves to Dynamics 365 and what stays in the archive or goes to the accounting program.
  • Before the move we clean the data: merge duplicate counterparties, fix phones and names, and mark old records the CRM does not need.
  • We make a trial load of a small part of the data, and your managers check clients and open orders on familiar examples before the full load.
  • For the transition both systems run in parallel: new sales go into Dynamics 365, and 1С/BAS stays at hand as a reference, so the team keeps selling.
  • We reconcile clients and open orders in Dynamics 365 against 1С/BAS on the same date; every difference is explained before the next step.
  • Only after that is the sales side of 1С/BAS switched off; the accounting part stays until your accountant moves to their new program, and the old database is kept as an archive.

Automation scenarios

01

One client, several cards

Before the same client sits in 1С/BAS under several spellings, and managers argue whose client it is.

After duplicates are merged before the move, and in Dynamics 365 the client has one card with the whole history.

02

Managers wait for the operator

Before to see what a client bought or which of his orders are still open, a manager asks the person who works in 1С/BAS.

After the client, his open sales and his history are in Dynamics 365, and the manager sees them himself.

03

Sales and accounting part ways

Before everyone thinks leaving 1С/BAS means the accountant loses their tool.

After sales work in Dynamics 365, and the accountant moves the books to the program they chose, without waiting for the sales side.

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
  • Dynamics 365's data connection is built on the open OData 4.0 standard, an OASIS standard for building and using REST-style interfaces — so it can be used across many programming languages and platforms, not only Microsoft's own tools.

    Source: learn.microsoft.com ↗ checked 2026-09-25
  • The daily request budget depends on the user's license: most paid Dynamics 365 and Power Platform licenses get 40,000 requests per license, per 24 hours.

    Source: learn.microsoft.com ↗ checked 2026-09-25
  • The daily budget counts every create, read, update, delete, assign and share operation, no matter whether it was triggered by a person or an internal system process, and no matter which protocol carried it.

    Source: learn.microsoft.com ↗ checked 2026-09-25

Limits

The limits come from both systems. Dynamics 365 counts every read, write and change of data against a daily budget tied to the licence: most full paid licences get 40,000 requests per 24 hours, lighter licences far fewer, and failed attempts count too. So a long history is loaded in portions under an account with a full licence. The Dynamics 365 documentation we rely on does not describe a ready import of a 1С/BAS database, so the data is exported from 1С/BAS through its open exchange interface, prepared and loaded step by step. Dynamics 365 Sales is a CRM: accounting and tax reporting from 1С/BAS do not move into it and need a separate accounting program chosen with your accountant. 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 sales stop during the move?
No. For the transition both systems run in parallel: new sales go into Dynamics 365, and 1С/BAS stays as a reference until the reconciliation shows the same figures.
What about accounting?
Dynamics 365 Sales does not keep the books. Sales move to the CRM, and accounting and tax reporting move to a separate accounting program that your accountant chooses; we agree the boundary at the audit.
Does our Dynamics 365 licence matter?
Yes. The daily request budget depends on the licence of the account the load runs under, and light licences get far fewer requests. We agree the account with your administrator before the start and load long history in portions.

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.