In 2026, a cloud-based 1C solution should be selected based on the supported configuration and release, the number of users and databases, and the terms for backup, migration, and data export. Articles 307, 315 and 317 of the Tax Code of the Republic of Kazakhstan regulate subsoil users’ expenses, while Article 659 of the Tax Code of the Republic of Kazakhstan regulates the fee rate for electricity consumption for digital mining purposes; these provisions do not establish rules for selecting, connecting, or migrating a cloud-based 1C solution (Articles 307, 315, 317, 659 of the Tax Code of the Republic of Kazakhstan).
What 1C in the cloud is and who it is suitable for
1C in the cloud is a way of working in which the infobase is hosted on the provider’s infrastructure and employees connect to it via the internet. The company does not need to deploy its own server for this database, but the procedure for updating the software, providing maintenance, and granting access must be stipulated in the agreement.
This format is suitable for organizations that need remote access for several employees, as well as accountants who maintain records for several companies. It may be convenient for small businesses without an in-house system administrator if the provider assumes responsibility for infrastructure maintenance and specifies the scope of its obligations.
Before selecting a service, obtain written confirmation of the following parameters:
- which 1C configurations and editions are available for connection;
- which configuration releases are supported by the cloud platform;
- how many concurrent sessions are permitted under the plan;
- how many infobases and organizations can be maintained;
- how platform and configuration updates are installed;
- which consultations and technical services are included in the price;
- how backups are created, stored, and restored;
- how to obtain a database export when the service is terminated.
The number of organizations, infobases, and users are different parameters. For example, one database may contain the accounting records of several organizations, while the number of registered users may differ from the number of employees working in the software at the same time. These limits should therefore be compared separately.
Also determine in advance whether employees need browser access, a thin client, data exchange with external systems, electronic documents, banks, and government services. The inclusion of a configuration in the cloud service’s list does not in itself confirm that all extensions, data processors, and integrations used by the company will work.
The cloud format does not eliminate the need for internal access control over the accounting database. The company must define users, their roles, the procedure for granting and revoking access, and the persons responsible for approving changes and restoring data. It is useful to formalize these conditions before connection so that the accounting department and the provider have the same understanding of the boundaries of responsibility.
1C:Fresh cloud: access, plans, and customizations
Search queries such as “1C Fresh cloud,” “1C Fresh in the cloud,” and “1C cloud Fresh” usually refer to a service model in which the software and infobase are hosted in cloud infrastructure and the user connects to them via the internet. The specific connection method—browser or thin client—is determined by the terms of the selected service and plan.
Comparing plans solely by the total subscription price is insufficient. The commercial proposal must separately specify the service period, the number of users, concurrent sessions and databases, the amount of disk space, the scope of consultations, the update procedure, and the cost of work not included in the subscription fee.
If the provider offers trial access, use it to test everyday operations. The accountant should open large document journals, generate standard and statutory reports, check printed forms, file uploads, bank data exchange, and simultaneous work by several users. The results of this test should be documented before paying for an extended service period.
Customizations to a cloud database may be restricted by the platform’s rules. Before migration, provide the supplier with a list of extensions, external data processors, modified printed forms, data exchanges, and background jobs. Obtain a written response for each item stating whether it is supported, whether adaptation is required, how long the work will take, and who is responsible for updates after a new release.
In practice, the decision to “buy 1C in the cloud” means purchasing access rights and a set of services under specified terms. Before concluding the agreement, request the procedures for registering users, changing the plan, providing technical support, processing requests, restoring the database, and terminating the service.
Pay particular attention to data exports. The agreement must clearly state the export format, the timeframe for providing it, the cost of this operation, and the parties’ actions after the subscription ends. If an export requires a preliminary update or special technical work, it is better to agree on this condition upon connection rather than when switching to another provider.
Separately compare the cloud configuration release with the release used by the company. For 2026, the current product line is represented by releases 3.0.74.x of “Accounting for Kazakhstan” and 3.1.37.x of “Payroll and Human Resource Management for Kazakhstan.” Before migration, not only the release number but also the possibility of sequentially updating the specific database, taking its modifications into account, is important.
How to migrate accounting or 1C:Trade Management to the cloud
Migration begins by identifying the configuration, edition, platform version, release, and customizations. The provider must confirm that it can accept such a database and describe the preparatory steps. If the source release cannot be uploaded directly, an update sequence is first prepared and the impact of the changes on extensions and data exchanges is assessed.
The migration time and cost depend on the database size, the condition of the information system, the number of customizations, the need for updates, and the data transfer method. A universal price and timeframe for every database would be incorrect: they are established after analyzing a copy or the technical description of the database.
Before work begins, agree on a cut-off point: the date and time after which users will stop entering documents into the old database. Otherwise, some transactions may remain only in the source system. The responsible employee must notify users of the period of unavailability and confirm that work has been completed before the final copy is created.
Before migration, the accountant should:
- Agree on the date and time when document entry into the old database will stop.
- Create a control backup and store it separately.
- Record the database configuration, edition, platform version, and release.
- Prepare a list of extensions, external data processors, data exchanges, and modified printed forms.
- Record the users, their roles, and access rights.
- Identify documents, reports, and indicators for control reconciliation.
- Designate the persons responsible for transferring, uploading, testing, and accepting the database.
After uploading, it is not enough merely to check that the software opens. Check the list of organizations, accounting policies, directories, account and register balances, the latest documents entered, numbering, closed periods, statutory reports, and user permissions. For integrations, perform a separate data exchange test without sending data in bulk.
The acceptance results can conveniently be presented in a table:
| Item to be checked | What to compare |
| Organizations and directories | Set of records, details, and availability to users |
| Balances and reports | Indicators in the source and migrated databases as of the same date |
| Latest documents | Availability, dates, numbers, posting status, and printed forms |
| Access rights | User roles and access to organizations and sections |
| Data exchanges | Connection settings and the result of a test operation |
| Extensions | Connection, purpose, and operation on the cloud release |
If 1C:Trade Management needs to be migrated to the cloud, the provider must confirm support for the specific edition and release of “Trade Management.” A general promise to host “any 1C solution” does not replace such confirmation. In the technical specification, state the edition, release, database size, operating mode, extensions, data exchanges, and number of users.
Before switching employees over, retain the source database and the reconciliation report. The old system should not immediately be used in parallel to enter new documents, as this creates two diverging versions of the accounting records. If temporary parallel access is necessary, determine in advance which database is the production database and who is authorized to modify it.
Backing up 1C to the cloud and resolving freezes
Cloud hosting and backup are separate service conditions. Before connecting, request the relevant procedure: how often backups are created, how long they are retained, where they are stored, who may request restoration, and how the result is confirmed. The agreement or its appendix must clearly describe the course of action in the event of data corruption or an erroneous change.
It is useful to provide for a copy accessible to the company itself. For this copy, determine the frequency of receipt, storage location, responsible employee, and restoration testing procedure. The mere existence of a file does not confirm that a functioning infobase with the required configuration and release can be deployed from it.
If a separate automatic archiving service is used, assess it based on the functions stipulated in the agreement: backup schedule, encryption, result notifications, retention period, restoration, and archive export. The name of a function or plan without a description of these conditions is insufficient to assess whether the backup arrangements are adequate.
Restoration should preferably be tested on a separate test database. After restoration, open the software and check the date of the most recent data, several documents and reports, and whether the responsible users can log in. The company establishes the frequency of such tests in its internal procedures, taking into account the intensity of work and the acceptable level of data loss.
If the browser version of 1C freezes, first record the time of the error, the user, and the operation being performed. You can then check the internet connection, try logging in again using another supported browser, or contact technical support. These steps help distinguish a local workstation issue from a database or cloud platform failure.
Clearing the browser cache with Ctrl+Shift+Delete may help with errors related to saved website data. Before deleting anything, check the selected categories and period: clearing passwords, cookies, and data from other websites may terminate active sessions and remove saved information. If the error recurs, send support a description of the actions performed and a screenshot of the error message.
If many users experience slower performance, do not run identical resource-intensive reports simultaneously on multiple workstations. First determine whether the issue affects all users, one organization, one report, or a specific period. Recording this information reduces diagnostic time and helps the provider reproduce the problem.
Frequently asked questions
Can I use 1C in the cloud from another city? — Yes, if the agreement provides for remote access and the workstation meets the service’s technical requirements. The user will need credentials, a stable internet connection, and approved connection tools.
Which applications are available in 1C:Fresh for Kazakhstan? — The list depends on the selected cloud platform and plan. Before paying, obtain confirmation of the exact configuration name, edition, and supported release, as well as the extensions and data exchanges used.
How much does 1C in the cloud cost? — The total amount consists of the plan price and the cost of additional work. The calculation must separately show the access period, number of users and databases, migration, updates, permission configuration, customizations, training, backups, and export upon termination of the service.
Can a cloud database be customized? — This depends on the platform’s rules and the customization method. Before migration, the provider must assess the extensions, external data processors, printed forms, and integrations, and then specify in writing which items are supported and the cost of adaptation.
Is a separate backup needed if the database is already in the cloud? — The decision is made based on the contractual backup procedure and the company’s internal rules. It is important to know how often backups are created, how long they are retained, the restoration procedure, and whether an export controlled by the company can be obtained.
How can I tell whether the migration has been completed successfully? — Perform an acceptance reconciliation of the source and cloud databases as of the same date. Compare organizations, balances, the latest documents, reports, user permissions, extensions, and data exchanges, and document the result before full-scale work begins.
Sources
When selecting a service, use the agreement, plan description, technical connection requirements, backup procedure, and written confirmation of support for the specific configuration, edition, and release. Article 307 of the Tax Code of the Republic of Kazakhstan defines the value balances of the group for expenses incurred by a subsoil user before the commencement of production; Article 315 regulates the allocation of expenses to non-contract activities; Article 317 covers the deduction of a subsoil user’s expenses for personnel training and the development of the regions’ social sphere; Article 659 establishes the fee rate for electricity consumption for digital mining purposes (Articles 307, 315, 317, 659 of the Tax Code of the Republic of Kazakhstan).