CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU

Moving from 1С/BAS to Salesforce

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

When a company's sales team grows out of 1С/BAS, Salesforce is often the next step. 1С/BAS is on the official prohibited software list, which makes the decision easier. The hard part is the data: years of 1С/BAS hold duplicate clients and orders nobody closed. We take that part: we look at what is really in 1С/BAS, clean it, make a trial load and let both systems run side by side until the figures match. Salesforce is usually set up by your own administrator or integrator, and we load the data into the structure they have built. Salesforce 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 Salesforce capabilities we rely on.

What we move

  • 1С/BAS → SalesforceCounterparties from 1С/BAS — companies and individuals with tax code and addresses — become client records in Salesforce, in the structure your administrator has set up; duplicates are merged before the load.
  • 1С/BAS → SalesforceContact people with phones and emails become contacts linked to their company, so the manager knows whom to call.
  • 1С/BAS → SalesforceCustomer orders that are not yet closed become open sales in Salesforce, so they are finished there rather than in 1С/BAS.
  • 1С/BAS → SalesforcePayments on those open orders move with them as information, so the manager sees what the client has already paid.
  • 1С/BAS → SalesforceSales 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

  • First your Salesforce administrator registers a separate access app for the load and grants it access through Salesforce's own sign-in; for new connections Salesforce now recommends its newer kind of such apps.
  • 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 Salesforce 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 Salesforce, and 1С/BAS stays at hand as a reference, so the team keeps selling.
  • We reconcile clients and open orders in Salesforce 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 Salesforce the client has one card with the whole history.

02

Afraid to switch

Before the move is postponed, because nobody knows what happens to orders in progress on the day of the switch.

After open orders move to Salesforce, both systems run side by side, and sales go on as usual.

03

Sales and accounting part ways

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

After sales work in Salesforce, 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
  • REST API gives programmatic access to Salesforce records, metadata and search without using the Salesforce interface itself.

    Source: developer.salesforce.com ↗ checked 2026-09-25
  • Access is authorised through OAuth 2.0 via a Connected App or External Client App; since Spring '26, creating new Connected Apps is restricted and Salesforce recommends External Client Apps instead (existing Connected Apps keep working).

    Source: developer.salesforce.com ↗ checked 2026-09-25
  • Salesforce Flow is a no-code automation builder that runs on the same platform as Apex code and can automate steps for any record type.

    Source: developer.salesforce.com ↗ checked 2026-09-25

Limits

The limits come from both systems. Salesforce caps the number of requests a day, and the ceiling grows with the number of user licences; no more than 25 long requests can run at the same time. So a long history is loaded in portions. The structure of data on the Salesforce side is your administrator's to decide; we prepare and load data under their rules. The Salesforce 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. Salesforce 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 Salesforce, and 1С/BAS stays as a reference until the reconciliation shows the same figures.
What about accounting?
Salesforce 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.
We already have a Salesforce administrator. What is your part?
The 1С/BAS side: we export the data, clean duplicates, check it with your people and load it by the rules agreed with the administrator. The Salesforce 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.