Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You are moving to the cloud (1C:Fresh service) or, conversely, taking your database out of the service "to yourself", and support asks: "Export the application data to a container and send the file." Or you are merging two databases, transferring settings between copies, preparing an archive before a major update. You open this processing tool — and get one packaged file with all your data (or unpack such a file back). This is not a "document", it's a service transfer tool. Below is how to use it so that nothing is lost.
Important right away. This is a technical processing tool. It does not create accounting entries, does not issue ESF/SNT, and has no printed forms. Its result is a data container file (usually
.zip/.xml) and an execution log. Therefore, the sections about entries, electronic documents, and printing below are adapted to the object's real behavior, not "drawn on".
1. Purpose
The processing tool exports all application data (of your information base or data area in the service) into a single container file and loads such a container back. It is used when transitioning "local database ↔ cloud", transferring an area between databases, and creating a technical dump for support. It is part of the standard subsystems library "Data Export and Import".
2. Where to find it
The direct path depends on whether you work in a local database or in the service:
- Local database (file-based/client-server): section "Reference Data and Administration" (or "Administration") → group "Maintenance" → "Data Export and Import". In the service model, the item may be called "Transition to service / from service".
- Direct call of the processing tool (for the administrator): "Functions for a technical specialist" → "Processing tools" → find it in the list.
1C navigation link (Main menu → "Service" → "Go by navigation link", paste the string):
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерКонтейнера
The menu item is visible only to a user with administrator rights. A regular manager or accountant does not have access to the processing tool — and that's correct: it works with the entire database as a whole.
2a. How to find out your release
Main menu (☰ icon or "orange circle" at the top) → "Help" → "About the program". In the window that opens:
- platform version (e.g.,
8.3.24.xxxx) — "1C:Enterprise" line; - configuration release — "Trade Management for Kazakhstan" line, e.g.
3.4.5.21 (3.4).
The instruction is written for 3.4.5.21. If you have a different release, the location of menu items may differ by a couple of steps, but the logic of container export/import is the same.
3. How to fill in (step by step)
The processing tool operates in two modes — Export and Import. The mode switch is the first thing you select.
"Export" mode
| Field / step | Why it's needed and what happens if you make a mistake |
|---|---|
| Mode = "Export data" (REQUIRED) | Sets the direction. Get the mode wrong — instead of creating an archive, you'll start wiping the database with an import. Check this first. |
| Container file (where to save) (REQUIRED) | Path and name of the .zip file. Save it to a disk with plenty of space — the container is comparable in size to the database. No rights to the folder or not enough space — the export will fail midway. |
| Export composition | Usually "all application data". If a choice is available — don't uncheck boxes carelessly: incompletely exported registers will cause discrepancies after import. |
| Export users / rights | Affects whether accounts get into the container. For moving "to yourself" it's usually left on; when transferring to support — check personal data policy. |
| Do not export history / service data | Reduces file size. Uncheck it — you lose part of object versions and service information. |
"Import" mode
| Field / step | Why it's needed and what happens if you make a mistake |
|---|---|
| Mode = "Import data" (REQUIRED) | Direction "from file to database". |
| Container file (what to import) (REQUIRED) | Path to a previously exported .zip. A file from a different configuration/incompatible release will result in a structure error. |
| Target database = EMPTY or archival copy (critical) | Import overwrites data. Never load a container into a working database with valuable data. First an archival copy (.dt), then the import. |
| Exclusive mode | All users must log out. If someone remains in the database — the import won't start or will be interrupted. |
Golden rule before importing: make an export to a
.dtfile ("Administration" → "Export information base"). This is your insurance in case the container turns out to be incomplete.
4. Worked example
Situation. "Astana-Trade" LLP (VAT payer, rate 16%) is moving from the local database "Trade Management for Kazakhstan" 3.4.5.21 to a cloud service. The database contains counterparty directories, inventory balances on account 1330, customer debt on 1210, sales documents for 2026. Everything needs to be transferred without loss.
Steps.
- The administrator logs into the database, logs out users, enables exclusive mode.
- Opens the processing tool → mode "Export data".
- Specifies the file:
D:\Exchange\astana-trade_2026-09-23.zip. - Leaves "all application data", clicks "Export".
- Receives a container of a size comparable to the database, and an execution log: "Export completed successfully, objects exported: N".
- In the cloud (empty) data area of the service, opens the processing tool → mode "Import data" → selects this file → "Import".
- At the end — the log "Import completed". Checks control totals: turnovers on account 6010 (sales income) and 7010 (cost of sales) in the new database matched the old one; the balance on 1330 — also matched.
What "moved" in control figures (before/after reconciliation, nothing should change):
| Indicator | Account | Before (local) | After (cloud) |
|---|---|---|---|
| Goods in warehouse | 1330 | 4,500,000 ₸ | 4,500,000 ₸ |
| Customer debt | 1210 | 1,850,000 ₸ | 1,850,000 ₸ |
| Supplier debt | 3310 | 980,000 ₸ | 980,000 ₸ |
| VAT payable (16%) | 3130 | 296,000 ₸ | 296,000 ₸ |
| Sales income for the period | 6010 | 12,400,000 ₸ | 12,400,000 ₸ |
About entries. The processing tool itself does not generate a single entry. It transfers already existing movements "as is". A correct export/import is when the reconciliation table before and after matches down to the tenge. If after import VAT at 16% on account 3130 "drifted" — the container is incomplete, repeat the export.
5. Types of operation
The processing tool provides two operations:
- Data export — packing all application data into a container (file).
- Data import — unpacking the container into the target (empty/archival) database.
In the service model, the same two operations are presented as "Transition to service" (exporting a local database for loading into the cloud) and "Transition from service" (exporting a data area from the cloud for local deployment).
6. What is generated during execution
- Container file (
.zip, containing an XML description of the data and attachments). This is the only "output document". - Execution log — messages about the number of exported/imported objects, warnings and errors. Save it: support uses it to diagnose problems.
- Target database data change — only in import mode: application data is overwritten with the container's contents.
What does not happen: the processing tool does not create accounting entries, does not issue ESF and SNT, does not send anything to the ESF IS, does not move accounting registers on its own. All entries, ESF, SNT, and register movements are the result of your regular documents (sale, receipt, invoice), which are simply transferred along with the database.
7. Printed forms
The processing tool has no printed forms — it's a service tool. Only the execution log goes "to print" here (it can be copied/saved to a text file) and, if necessary, an error log for submission to technical support.
8. Common errors
| Message / symptom | Cause | How to fix |
|---|---|---|
| "Failed to complete the operation because the database is in use by other users" | Import requires exclusive mode | End all sessions: "Administration" → "Active users" → disconnect everyone, set a lock on starting new sessions. |
| "Error importing data: incompatible configuration version" | Container exported from a different release/configuration | Bring releases to the same one (3.4.5.21 ↔ 3.4.5.21) and repeat; a container from "Accounting" will not load into "Trade Management". |
| "Not enough disk space" / export fails | Not enough space for the .zip |
Free up disk space, container size ≈ database size; export to a disk with headroom. |
| "Access rights violation" | User without full administrator rights | Log in as a user with the "Administrator" profile. |
| After import turnovers (6010/7010) and VAT (3130) don't match | Incomplete export / interrupted process | Do not use such a database. Repeat the entire export, check the log for warnings. |
| "File is corrupted / invalid container structure" | File not fully downloaded or corrupted archive | Re-download the file, compare its size with the original, use a reliable channel when transferring. |
9. FAQ
1. Does this processing tool create accounting entries? No. It only transfers data. All entries, including VAT at 16% on account 3130 and cost of sales on 7010, are created by your regular documents and move together with the database unchanged.
2. Does it issue ESF or SNT? No. ESF and SNT are generated by sales/invoice documents and sent to the ESF IS. The container processing tool has nothing to do with electronic document flow — it only transfers already issued documents.
3. Can a container be loaded into a working database with data?
No. Import overwrites application data. Load only into an empty or definitely non-valuable/archival database. Make a .dt backup before any import.
4. How is this different from exporting to a .dt file?
.dt is a full dump of the information base using platform tools (configuration + all data), and it's tied to the platform version. This processing tool's container is an export of application data at the applied solution level, used for "local ↔ service" transitions and transferring areas.
5. Are users and passwords transferred? Depends on export settings. Usually there's a checkbox for users and rights. For moving "to yourself" it's usually left on; when transferring the file to support, consider personal data.
6. Why don't I see this item in the menu? It's available only to the administrator. Under manager/accountant rights, the processing tool is hidden because it works with the entire database as a whole.
7. How much time and space does the export take? Time and size are comparable to the database's volume: for a large trade database this can be gigabytes and dozens of minutes. Keep at least the database's size worth of free disk space.
8. What to do if the amounts don't match after import? Such a database cannot be used. Return to the backup copy, repeat the entire export, carefully read the log — it will contain warnings about incompletely exported objects. Control reconciliation: balances on 1330, 1210, 3310 and turnovers 6010/7010 before and after must match down to the tenge.
9. Can two databases be merged with this processing tool? It does not perform a direct "merge" — import overwrites the target database. Other mechanisms (exchange, synchronization) are used for merging data. The container is a transfer of the entire database, not a blending in.
10. I opened the processing tool via the navigation link, but it's empty/gives an error — why?
The link e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерКонтейнера opens the service object directly. Work with it as an administrator, and preferably through the standard "Data Export and Import" item — there you get the correct wizard interface.
10. Related documents and mechanisms
- Information base export/import (
.dt) — "Administration" → corresponding commands. Do this before any container import as insurance. - Data synchronization / exchange — if you need to not transfer the entire database, but regularly exchange part of the data between databases.
- Transition to service / from service — a service "wrapper" over this same processing tool when working in 1C:Fresh.
- Backup — scheduled backups; the container does not replace them, but supplements them during the move.
This processing tool is not "entered on the basis of" a document and does not generate documents — it services the entire database at once.
How to find out your release
Main menu → "Help" → "About the program": this shows the platform version (1C:Enterprise 8.3.x) and the configuration release. If it differs from the one specified below, check against the description of your version.
This guide was prepared for "Trade Management for Kazakhstan", release 3.4.5.21 (edition 3.4). Numerical norms (VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸) are given as of 2026.