---
title: "Data Export Manager processing in UT for Kazakhstan 3.4.5.21: exporting and importing IB data"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-24
canonical: https://buhgpt.kz/suraqtar/obrabotka-menedzher-vygruzki-dannyh-informacionnoy-bazy-v-en
source: BuhGPT
---

# Data Export Manager processing in UT for Kazakhstan 3.4.5.21: exporting and importing IB data

> **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). Your implementation partner called and said: "Send us a database export, let's see why the warehouse balance isn't closing." Or you're moving to a new server and need to transfer data without a full 

---

Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).

Your implementation partner called and said: "Send us a database export, let's see why the warehouse balance isn't closing." Or you're moving to a new server and need to transfer data without a full SQL backup. Or 1C tech support asks for the "infobase data export file", not the full dt-file. In all these cases, you open exactly this processing. It's not an accounting document — there are no amounts, VAT, or postings here. It's a service tool: it exports the contents of the infobase into a structured file (an archive with XML) and can load it back. Next — how to use it without losing data or breaking the database.

⚠️ Important from the first paragraph: this processing changes or completely overwrites data during loading. Work with it only with administrator rights, in exclusive mode, and always make a backup copy (.dt via Designer) before loading.

1. Purpose

The "Infobase Data Export Manager" processing transfers infobase data to an export file and loads it back. It is used when transferring a database between servers/file variants, sending data to tech support, or migrating with an identical or compatible configuration. This is a technical (service) object — it does not create accounting entries.

2. Where to find it

The processing is a service one, so it is not in the regular sections of the command interface. It can be opened in two ways:

- Via the functions menu: "Main" (arrow button in the top left corner) → "Functions for a technical specialist" (mode must be enabled in "Settings" → "Options" → "Display the All functions command") → "Processing" section → "Data export load infobase data export manager".

- Via a navigation link (fastest way): "Service" / "Main" menu → "Go to navigation link" and paste:

e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиДанныхИнформационнойБазы

If there is no "All functions" item: "Service and settings" (gear) → "Settings" → "Options" → enable "Display the 'All functions' command".

2a. How to find out your release

"Main" / gear → "Help" → "About the program". In the window that opens you will see:

- platform version (e.g. 8.3.2x.xxxx) — the "1C:Enterprise" line;

- configuration release — the "Trade Management for Kazakhstan" line, edition 3.4, version 3.4.5.21.

Check the instructions against these exact numbers: the export/load mechanism has changed between platform releases, and the processing's behavior depends on the version.

3. How to fill in (step by step)

There are no "document fields" here in the usual sense — there are two modes of operation: Export and Load. Let's look at each parameter: why it's needed and what happens if it's set incorrectly.

"Data Export" mode

Parameter
Required
Purpose and what happens on error

Export file (path and name)
Yes
Where to save the result. Specify a local drive with sufficient free space. If you specify a network folder without write permissions, the export will fail with a save error. The extension is usually .xml/.zip depending on the mechanism.

Data composition (whole infobase / selective)
Yes (default — whole infobase)
Determines what will be included in the file. If you export selectively and forget related objects, loading at the destination will produce broken references. For a full transfer, leave "whole infobase".

Data only / data and settings
Depending on the situation
Affects the transfer of user settings and service information. For a full database clone, enable everything.

Compression / packing into an archive
No
Reduces the file size. On large databases it saves transfer time.

Procedure:

- End all user sessions, log in as administrator.

- Make a backup copy via Designer ("Administration" → "Export infobase" → .dt).

- Open the processing, select "Export" mode.

- Specify the destination file and data composition.

- Click "Export" and wait for the success message.

"Data Load" mode

Parameter
Required
Purpose and what happens on error

Export file (source)
Yes
A file produced by this same processing. It will not accept a different format (e.g. a regular .dt).

Load mode (into current / with clearing)
Yes
Key parameter! "With clearing" deletes current data before loading. Get it wrong and you'll lose a working database. Only load into an empty or definitely unneeded infobase.

Exclusive mode
Yes (mandatory)
Loading requires that there are no other sessions in the database. If someone is working — the operation will not start.

Procedure:

- Make sure the destination configuration is compatible with the source (same edition 3.4, preferably the same release).

- All users have logged out, and there is a fresh copy of the destination database.

- Open the processing, "Load" mode, specify the file.

- Click "Load", wait for completion, and restart the program.

4. Worked example

Situation. Bereke Trade LLP (Almaty) works in a file-based database of Trade Management for Kazakhstan 3.4.5.21. The accountant is transferring the database to a new server (client-server variant, same release) and wants to give the developer only the data, without service settings.

Steps and result:

- Backup: Bereke_2026-09-23.dt (200 MB) — in case of rollback.

- Opened the processing, "Export" mode, composition — "whole infobase, data only", file Bereke_data.zip.

- The export took ~4 minutes, resulting in an archive Bereke_data.zip of 78 MB.

- On the server, an empty infobase was created with the Trade Management for Kazakhstan 3.4.5.21 configuration.

- In the new database, opened the processing, "Load" mode, specified Bereke_data.zip, "with clearing" mode (database is empty), exclusively.

- Loading — ~6 minutes, restart.

- Check: "Organizations" catalog — 1 organization; "Counterparties" — 342 entries; balances on account 1330 "Goods" and 1210 "Short-term receivables from customers" matched the source database; VAT in sales remained 16% (Kazakhstan 2026 rate).

Postings: the processing does not create them. It transfers movements and balances already existing in the database as is — amounts, rates, and account correspondences are not recalculated. If in the source database a sales document produced:

Dt
Ct
Amount
Description

1210
6010
1,160,000 ₸
Revenue from sales (excl. VAT)

1210
3130
185,600 ₸
VAT 16% payable

7010
1330
700,000 ₸
Cost of goods sold written off

— then exactly these same movements will end up in the destination database after loading. The processing does not calculate anything itself; the source documents are responsible for the correctness of the figures.

5. Types of operation

- Data export — saving the infobase contents to a file (fully or selectively).

- Data load — restoring data from a file into the current or an empty infobase, with or without clearing.

There are no other types of operations for the processing: these are two mirror functions of the same mechanism.

6. What is generated on posting

The concept of "posting" does not apply to this processing — it is not a document. The result of its work:

- On export: an export file (an archive with an XML structure) that can be transferred, saved, loaded into another database.

- On load: a changed infobase state — all objects (catalogs, documents, registers, movements, balances) are transferred.

What the processing does NOT generate (important to understand):

- accounting entries — no;

- electronic documents ESF (IS ESF) and SNT — no; it does not interact with IS ESF and does not create tax documents;

- separate register movements on its own behalf — no; it only transfers already existing movements.

7. Printed forms

The service processing has no printed forms. There is only a service log/execution journal (success or error messages), displayed in the message window — it can be copied and sent to tech support. It is not possible to print acts, invoices, or reports through this processing — the corresponding configuration documents are used for that.

8. Common errors

"The operation cannot be performed because other users are working with the database"
Loading requires exclusive access. End all sessions ("Administration" → "Active users"), close background jobs, and retry.

"The export file has an invalid format" / "Failed to read the file"
You are trying to load a different format (e.g. a regular Designer .dt or a corrupted archive). Only load a file created by this same processing; make sure the archive is not corrupted.

"The source configuration does not match the destination configuration"
Releases have diverged. Update the destination to the same version (3.4.5.21) or a compatible one and repeat the loading.

"Insufficient disk space" / file write error
The export didn't fit. Free up space or export to another drive; enable archive compression.

Data was loaded, but rights/users have "disappeared"
You exported in "data only" mode. Settings and rights are not transferred that way — either export with settings, or set up rights again at the destination.

After loading, the database asks for "Infobase update"
This is normal: on first login the configuration runs scheduled handlers. Log in as administrator and wait for completion.

9. FAQ

Is this the same as "Export infobase to a .dt file" from Designer?
No. .dt is a full snapshot of the infobase together with the configuration, and only works between identical platforms/configurations. This processing exports data into a portable format and is useful when .dt is excessive or incompatible.

Does the processing create accounting entries?
No. It's a service tool. All postings, balances, and amounts remain exactly as they were generated by the documents in the source database.

Does it affect ESF and SNT?
Not directly. It does not send data to IS ESF, does not issue electronic invoices or SNT. Only objects already existing in the database and their statuses are transferred.

Do I need to make a backup before loading?
Mandatory. Loading "with clearing" destroys current data. Make a .dt via Designer and make sure the copy is readable.

Can I load data into a database with a different configuration release?
Only if the releases are compatible. Safe — when edition 3.4 matches and the release is the same, 3.4.5.21. If there is a discrepancy, align the versions first.

Who can run this processing?
A user with administrator rights (full rights). It is not available to a regular manager or accountant without administrative rights.

Will tax and VAT rates change after the transfer?
No. The Kazakhstan VAT rate of 16%, MRP 4,325 ₸, minimum wage 85,000 ₸, and all accounting parameters are database data and settings; they are transferred "as is". The processing recalculates nothing.

Why aren't users and interface settings visible after loading?
Most likely, the export was done in "data only" mode. Settings, rights, and personal parameters are transferred separately — either include them in the export composition, or restore them manually.

Can I export only part of the data, e.g. one warehouse?
The mechanism is primarily designed for a full transfer. Selective export is possible, but risky: related objects (documents, registers) may not be included in the file, and broken references will appear at the destination. For partial tasks, data exchange or reports are more reliable.

Does exporting a large database take a long time?
It depends on the volume and disk: a few minutes for databases of tens to hundreds of MB, longer for larger ones. Perform it outside working hours in exclusive mode.

10. Related documents and mechanisms

- .dt export/import (Designer) — an alternative for a full infobase snapshot; use it for a backup copy before loading.

- "Data Export and Load" processing — a related mechanism; this processing is its export manager.

- "Data synchronization" / exchange plans — for regular two-way exchange between databases (unlike the one-time export-load here).

- Scheduled "Infobase update" — runs automatically on first login after loading.

No other documents are entered based on this processing, and it itself is not entered "based on" anything — it is a standalone service tool.

How to find out your release

"Main" → "Help" → "About the program": it shows the "1C:Enterprise" platform version and the configuration release. This instruction is current for "Trade Management for Kazakhstan", edition 3.4, release 3.4.5.21. With a different release, the behavior of the export/load mechanism may differ — check the "About the program" window.

Prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (ed. 3.4). Kazakhstan 2026 calculation parameters: VAT 16%, MRP 4,325 ₸, minimum wage 85,000 ₸.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_