---
title: "Export and import of data (information base data loader manager) in Trade Management for Kazakhstan 3.4"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-24
canonical: https://buhgpt.kz/suraqtar/vygruzka-i-zagruzka-dannyh-menedzher-zagruzki-dannyh-info-en
source: BuhGPT
---

# Export and import of data (information base data loader manager) in Trade Management for Kazakhstan 3.4

> **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). Your database has "bloated," the platform on the new server is a bit newer, and the usual export to .dt throws an incompatibility error when loading. Or you need to transfer not the entire database, 

---

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

Your database has "bloated," the platform on the new server is a bit newer, and the usual export to .dt throws an incompatibility error when loading. Or you need to transfer not the entire database, but a bundle of files — to give a copy to an auditor, spin up a test database in the cloud, or move between two identical configurations without direct access to the database file. This is exactly what the "Data Export Import Data Loading Manager for Information Base" processing is for. This is a service tool: it doesn't create postings and doesn't print documents — it carefully "photographs" the database data into a portable set and then restores it in another database.

⚠️ The main thing you need to know before the first click: data loading completely replaces the data in the receiving database. This is not an "addition" or a "merge." Always load into an empty or clearly unneeded database and always have a fresh .dt backup copy.

1. Purpose

The processing exports information base data into a portable bundle (a set of XML files packed into an archive) and loads such a bundle into another database of the same configuration. It is used for transferring data between identical databases, migrating to the cloud/another server, and creating copies for development and audit when the standard .dt export is not applicable.

2. Where to find it

This is a service processing; it has no menu item in the regular cashier/accountant interface. Open it in one of the following ways:

- Main menu (☰) → All functions → Processing → "Data Export Import Data Loading Manager for Information Base."
(If there is no "All functions" item — enable it: Main menu → Tools → Options → "Display 'All functions' command" checkbox.)

- Via a navigation link. Copy it, then Main menu → File → Go to navigation link (or Ctrl+click on the link in the support chat):

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

Full (administrative) rights are required to work with it — a regular user will not be able to open the processing.

2a. How to find out your release

Main menu (☰) → Help → About the program. The window that opens shows:

- the platform version (e.g., 1C:Enterprise 8.3.24.xxxx);

- the configuration release — a line like Trade Management for Kazakhstan, edition 3.4 (3.4.5.21).

These two numbers determine which version the instruction applies to and whether the databases are compatible for transfer.

3. How to fill in (step by step)

The processing window is divided into two operations — Export and Import. Fill in only the one you are currently performing.

Data export

Field / element
Why it's needed and what happens if you make a mistake

Export file (required)
The path and name of the resulting bundle file (.xml or .zip). If you specify a network drive that drops out, the export will be interrupted midway; choose a local drive with enough free space (the bundle can be larger than a .dt file).

Composition of exported data
By default, the entire database is exported. If you uncheck some metadata objects, this data will be missing in the receiver — and related documents may not be restored. Change the composition only if you clearly understand the dependencies.

Export information base users
The list of users and their settings. If unchecked, the data will arrive in the receiver "without people," and logins will need to be re-created.

Click "Export data." Wait for the success message — do not close the window early.

Data import

Field / element
Why it's needed and what happens if you make a mistake

Import file (required)
The very bundle obtained during export. If you substitute a file from a different edition/configuration, the import will stop with an incompatibility error.

Receiving database
This is the currently open database. Make sure you have opened the test/new database, not the working one: the data will be overwritten with no way to "undo."

Overwrite confirmation
The processing will warn that existing data will be replaced. Agree only after you have made a .dt copy of the receiver.

Click "Import data," confirm the overwrite, wait for completion, and restart 1C — you need to re-log in to the session after loading.

Mandatory rule: both export and import are performed in exclusive mode (no one else is working in the database). Otherwise, you will get a lock error or an incomplete bundle.

4. Worked example

Task. The accountant of LLP "Astana-Trade" is transferring the working database from an office computer to the cloud. The platform in the cloud is newer, so loading a .dt file is impossible ("format version incompatibility"). The configuration is the same — 3.4.5.21.

Step 1. Export (on the office PC).

- Opened the processing → "Export" operation.

- Export file: D:\Transfer\astana_2026-09-23.zip.

- Composition — the entire database, "Export information base users" — enabled.

- Clicked "Export data." Received an 1.8 GB archive after 12 minutes.

Step 2. Preparing the receiver (in the cloud).

- Created an empty database from the "Trade Management for Kazakhstan 3.4.5.21" template.

- Immediately made a .dt copy of it in case a rollback is needed.

Step 3. Import.

- Opened the processing in the cloud database → "Import" operation.

- Import file: the astana_2026-09-23.zip uploaded from the office.

- Confirmed the overwrite → "Import data."

- Restarted 1C upon completion.

Step 4. Verification after transfer. Checked key balances to make sure the data arrived intact (figures — from a working database in Kazakhstan, 2026):

What was checked
Value in the source
Value in the receiver

Inventory balance, account 1330
4,812,500 ₸
4,812,500 ₸

Cash on current account, 1030
1,260,000 ₸
1,260,000 ₸

Accounts receivable, 1210
980,000 ₸
980,000 ₸

Accounts payable to suppliers, 3310
1,540,000 ₸
1,540,000 ₸

VAT payable (rate 16%), 3130
336,000 ₸
336,000 ₸

The balances matched down to the tenge — the transfer is correct.

Important note about postings. The processing itself does not generate accounting postings. It transfers already existing entries "as is." The table above does not show postings generated by the processing, but account balances that you check to confirm the completeness of the transfer. For example, a previously posted sale in the database will retain its posting Dr 1210 Cr 6010 for the revenue amount and Dr 3130 Cr … for 16% VAT — the processing simply transfers it unchanged.

5. Types of operation

The processing provides exactly two operations:

- Data export — generating a portable bundle from the current database.

- Data import — restoring the bundle into the current database with complete replacement of its data.

Additionally, you can control the export composition (the entire database or selected metadata objects) and export of information base users.

6. What is generated when processed

This is a processing, not a document — it has no concept of "posting." The result of the operation:

- On export — a bundle file .xml/.zip on disk. No entries are created in the source database, and the source data is not changed.

- On import — the receiver's data is completely overwritten with the contents of the bundle: catalogs, documents with their register entries, charts of accounts, settings, and, if the option is enabled, information base users.

What the processing does not do: it does not create new postings, does not generate an e-invoice (ESF IS) or a waybill (SNT), does not send electronic documents, and does not recalculate taxes. All previously generated e-invoices/waybills and register entries are transferred exactly as they were at the time of export.

7. Printed forms

The processing has no printed forms of its own — it doesn't print anything. Its only "output" is the data bundle file on disk. If you need a document for an auditor after the transfer, print it from the already transferred documents in the receiving database (for example, an invoice or an act from the corresponding sales document).

8. Common errors

"Data loading is only possible in exclusive mode"
There are active sessions in the database. End all sessions (Administration → Active users) and log in exclusively, then repeat the import.

"Configuration structure mismatch" / "Source configuration does not match receiver configuration"
The bundle was exported from a different release or a different configuration. Update the receiver to the same release (3.4.5.21) from which the export was made, and try again. This mechanism does not transfer data between different configurations.

"Not enough disk space" / export breaks off
The bundle is larger than a .dt file. Free up space or specify a different local drive in the "Export file" field. Do not export to an unstable network resource.

"Access rights violation"
The processing was launched by a user without full rights. Log in with an account that has the administrator role.

After loading, users "disappeared" / can't log into the database
The "Export information base users" checkbox was unchecked during export. Re-create the users in Administration → User and rights settings, or redo the export with the option enabled.

Data was loaded, but reports are "empty"
No restart was performed after loading. Fully close and reopen 1C.

9. FAQ

What is the difference between this processing and exporting to .dt?
.dt is a binary snapshot rigidly tied to the platform version: if the receiving platform is a bit newer, the load may fail. This processing's XML bundle is transferred between different platform versions of the same configuration, which is why it is used when a .dt file "won't take."

Can data be transferred from Trade Management for Kazakhstan to "Accounting for Kazakhstan"?
No. This is a transfer mechanism between identical configurations. To switch to a different configuration, you need specialized conversion/transfer processing, not this tool.

Will the import add data to what already exists in the database?
No. The import replaces the receiver's data entirely. Everything that was in the database before the import will be lost if there is no backup copy.

Will the processing generate e-invoices and waybills again?
No. Previously issued e-invoices and waybills are transferred in their original form. The processing does not create any new electronic documents and does not send anything to the ESF IS.

Do users need to stop working?
Yes, exclusive mode is required for both export and import. Otherwise, the bundle will be incomplete or the import will not start.

Will the processing recalculate taxes for 2026 rates (16% VAT, individual income tax, mandatory pension contributions)?
No. The processing does not recalculate anything — it transfers amounts and entries as is. The correctness of rates is the responsibility of the documents and accounting policy settings in the database itself.

Why does 1C ask for a restart after loading?
The entire content of the database changes, including current session settings. A restart is needed so the application re-reads the current data. You cannot work in the database before restarting.

Can only catalogs be exported, without documents?
Technically, the export composition is configured by metadata objects, but excluding documents while keeping registers results in inconsistent data. For a working transfer, export the entire database; a partial composition is only for debugging tasks and with a full understanding of the relationships.

Is this a replacement for regular backups?
No. For daily backups, use .dt exports or server-based archiving. This processing is used selectively — for transfer and migration.

What to do if the import is interrupted midway?
The receiving database is left in an inconsistent state. Restore it from the .dt copy, eliminate the cause (disk space, exclusive mode, matching releases), and repeat the import.

10. Related documents and tools

- Basis for the operation: the export is made from a ready, verified source database; the processing has no separate basis document.

- What complements it:
- Backup to .dt (Configurator → Administration → Export/Import information base) — a mandatory "safety" step before importing.

- Active users / ending sessions (Administration) — to enter exclusive mode.

- User and rights settings (Administration) — if users were not transferred.

- Configuration update — to align the source and receiver releases to 3.4.5.21.

- What is done after the transfer: reconcile balances of key accounts (1030, 1210, 1330, 3310, 3130), check document journals and the correctness of e-invoices/waybills, and, if necessary, reconfigure data exchanges and equipment connections.

How to find out your release

Main menu (☰) → Help → About the program. The configuration line will show the edition and release number, and the platform line will show the 1C:Enterprise version. Check both numbers: data transfer with this processing is only possible between databases of the same configuration release.

This guide was prepared for "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21.

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