---
title: "Processing \"Data Export Import: User Settings Export Manager\" in UT for Kazakhstan 3.4.5.21"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-24
canonical: https://buhgpt.kz/suraqtar/obrabotka-vygruzka-zagruzka-dannyh-menedzher-vygruzki-nas-en
source: BuhGPT
---

# Processing "Data Export Import: User Settings Export Manager" in UT for Kazakhstan 3.4.5.21

> **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You updated the database or deployed a copy on a new server — and get a flood of calls: one person's favorite links disappeared, another's columns in the item list got "shifted", a third's sales repo

---

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

You updated the database or deployed a copy on a new server — and get a flood of calls: one person's favorite links disappeared, another's columns in the item list got "shifted", a third's sales report opens in a different grouping than the one they set up over the past six months. Form settings, filters, favorites, history — all of this is personal user data, and it is easily lost when the database is transferred. It's the processing "User Settings Export Manager" that is responsible for transferring this "personal baggage". This is not an accounting document or a report — it is an administrative utility that transfers interface settings from one information base to another so that people don't have to set up their workspaces again.

Right away, so you don't waste time searching: this processing does not create journal entries, does not generate an ESF or SNT, does not calculate VAT, IIT or OPV, and has no printed forms. It works only with user settings. Below is how to use it and what to expect from it.

1. Purpose

The processing exports to a file and loads back the personal settings of users: form and list settings, filters, favorites, history, report settings, home page. It is used when transferring a database, merging databases, updating via export/import, and when restoring an individual user's workspace.

2. Where to find it

The processing is a utility one, so it is not in the regular section menu. It can be opened in two ways.

- Via the menu: "Master data and administration" → "Maintenance" → the "User settings" / "Data export and import" block. In standard configurations it is called from the data transfer wizard, not from a separate button.

- Directly via a navigation link (the most reliable way): "Main menu" (the ≡ icon in the upper-left corner) → "File" → "Open" is not available for configuration processing objects, so use "Tools" → "Go to navigation link" and paste:

e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиНастроекПользователей

It's convenient to save the link to favorites — then the processing is always at hand.

Only a user with administrator rights may open it. A regular sales manager doesn't need the object and, as a rule, doesn't have access to it.

2a. How to find out your release

"Main menu" (≡) → "Help" → "About the program". In the window that opens: the "Platform" line shows the 1C:Enterprise platform version, the "Configuration" line shows "Trade Management for Kazakhstan", the edition and release (you should have 3.4.5.21). If your release is lower, the location of menu items and the set of transferable settings may differ.

3. How to fill in (step by step)

The processing form is simple: mode selection, user filter, and file path. Let's go through each field — why it's needed and what happens if it's filled in incorrectly.

Field / element
What it's for
What happens if filled in incorrectly

Mode: "Export" / "Import" (required)
Determines the direction: save settings to a file or merge them into the database
If you select "Import" instead of "Export" — instead of saving, you will overwrite the current settings with the old ones from the file

Users (required)
List of users whose settings are processed. You can select all or specific ones
If you forget to check a user — their settings will not be transferred, their workspace will remain empty

Export file (required)
Path to the settings file (usually with a .zip extension or a service extension)
If you specify a nonexistent path when importing — the processing will not find the data; if exporting to a protected folder — it will not be able to write the file

Set of settings
Checkboxes: form settings, filters, favorites, history, report settings, home page
If you uncheck a needed checkbox — that category will not go into the file and will not be restored

Replace existing settings
Controls whether to overwrite the user's already existing settings
If you leave it enabled when importing into a working database — you will overwrite fresh settings with old ones from the file

Workflow:

- Open the processing in the source database.

- Mode — "Export". Check the required users (for a full transfer — all of them).

- Check the set of settings — usually everything is left checked.

- Specify the file path and click "Export". Wait for the success message.

- Transfer the file to the target database.

- Open the processing there, mode — "Import", specify the file, match the users (important: the logins in the databases must match), and click "Import".

4. Worked example

Situation. Trading company "Alatau-Trade" is moving from a file-based database to a 1C server. The database has 12 active users. The chief accountant has set up the "Sales of Goods and Services" list with the columns "Counterparty", "Amount", "VAT rate 16%" and a filter by organization; the manager has a home page with sales widgets.

Administrator's actions:

- In the old database: mode "Export", all 12 users checked, set — all categories, file nastroiki_2026-09-23.zip.

- The processing saved the settings of all 12 people into a single file.

- In the new server database: mode "Import", the same file selected, users matched automatically by matching logins, "Replace" checkbox enabled (the database is new, there is nothing to replace).

- After importing, the chief accountant opens the "Sales of Goods and Services" list — columns and filter are in place; the manager sees their home page.

There are no journal entries. This is a fundamental point: the processing does not affect accounting and tax accounting registers. No amounts (for example, sales 6010, cost of sales 7010, VAT payable 3130 at the rate of 16%) are affected by its operation — only the appearance of workspaces is transferred. If after the transfer you need to verify that the accounting data itself is intact, this is done by other means (register reconciliation, reports), not by this processing.

5. Types of operation

The processing provides two operations:

Operation
What it does

Export settings
Collects the personal settings of the selected users and saves them to a file

Import settings
Reads the file and restores settings for matched users in the current database

Additionally, the set of categories in the export is adjustable: form and list settings, user filters, favorites, usage history, report variant settings, home page content.

6. What is generated during operation

- No journal entries — the processing does not create movements on accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010 or any others) or on accounting and tax accounting registers.

- No electronic documents are created — this processing does not generate ESF in the ESF IS or SNT; it has no relation to exchange with government authorities.

- What is actually generated on export: a settings file (archive).

- What changes on import: records in the system settings storages of the current database (form settings, filters, favorites, history, report variants) for the selected users.

7. Printed forms

The processing has no printed forms. It is not intended for printing documents — transferring the appearance of reports and printing them will be done by the user using their regular tools after the settings are imported.

8. Common errors

"User not found in the target database" — the file contains settings for a login that does not exist in the new database. First create a user with the same name in "Master data and administration" → "User and rights settings" → "Users", then repeat the import.

"Insufficient rights to perform the operation" — the processing was launched by a user without administrator rights. Log in with an account that has full rights.

"Failed to write the file to the specified directory" — the path is not writable (for example, a system folder). Choose a directory to which you have access, such as your desktop or personal folder.

Settings were imported, but nothing changed for the user — the "Replace existing settings" checkbox was unchecked during import, and the user already had their own settings. Repeat the import with replacement enabled (deliberately, so as not to overwrite something needed).

The file won't open / "Invalid data format" — the file was created in an incompatible release or was corrupted during transfer. Re-export from the source on the same release and transfer the file without modification (do not unpack the archive manually).

9. FAQ

Does this processing create accounting entries?
No. It transfers only personal interface settings. It does not touch journal entries, accounting registers, or amounts.

Does it generate ESF or SNT?
No. This processing has nothing to do with issuing electronic invoices in the ESF IS or with waybills for goods.

Are the documents and reference lists themselves transferred?
No. Sales, receipts, counterparties, items — this is accounting data, transferred by other mechanisms. This processing is responsible only for user workspace settings.

What exactly gets included in the export?
Form and list settings, user filters, favorites, history, report variant settings and home page content — for the selected users.

Do users need to stop working during export?
For export — not necessarily, you're simply taking a "snapshot" of the settings. For import into a working database, it's better to do this when the affected users are not working, so their current settings don't conflict with the ones being imported.

The logins in the databases differ — how do I transfer the settings?
Automatic matching is done by matching user names. If the names differ, make them the same in the target database before importing, otherwise the settings won't be matched.

Can I transfer the settings of just one person?
Yes. In the user list, check only that person — the file will contain the settings of only that user.

Who is allowed to run the processing?
Only a user with administrator rights. Regular employees don't need it and usually don't have access to it.

Will the import overwrite my current settings?
It depends on the "Replace existing settings" checkbox. Enabled — it will replace; disabled — it will only add what's not already there. In a working database with real users, be careful with replacement.

Does the processing have a printed form?
No, it has no printed forms.

10. Related objects

- What it's used based on: the processing is called as part of the information base transfer and update mechanism ("Data export and import" in the "Master data and administration" → "Maintenance" section), as well as when deploying a database copy.

- What it works together with: the "Users" reference list ("User and rights settings") — settings are matched precisely against these accounts; the system settings storages of the current database.

- What is entered after it: it does not generate separate "based on" documents — the result of its operation is visible immediately in the user interface.

How to find out your release

"Main menu" (≡) → "Help" → "About the program". The "Configuration" line will show the name and release, the "Platform" line — the 1C:Enterprise version. The instructions are current for release 3.4.5.21.

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

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