Data transfer is a very important process in any accounting system, the 1C 8.3 and 8.2 platform is no exception. Below we will look at instructions on the easiest way to transfer data from one system to another that has a similar configuration (for different configurations, you can use a tool for programmers - or).

Before any action is necessary, the changes are irreversible!

The easiest and most convenient way to transfer data from 1C 8.3 to 1C 8.3 Accounting 3.0 is to use the processing Upload and load data in XML format (download - for 8.2 or for 1C 8.3 or on ITS). The treatment is universal and suitable for any configuration.

We won’t go into details; let’s look at step-by-step instructions for migrating data using this processing using the example of the simplest transfer of goods.

Uploading data to XML

First of all, let’s open processing in the source database (from where we will unload goods) and look at the interface:

Get 267 video lessons on 1C for free:

You must immediately fill in the “File name” field - a new data file will be created along this path, which we will upload to the receiver database. Just below, in the tabular section “Data for uploading”, you need to select the data that we want to upload from the database.

After selecting an object from the left table part, you can apply selection in the right table part:

In our example, I want to unload all products with the name “Rake”.

Once all the settings have been completed, the data can be uploaded. To do this, click on the “Upload data” button:

Loading data from xml into 1s 8.3

The data has been unloaded from the source database; now it needs to be transferred to the destination database.

To do this, you need to start processing already in the database into which you need to load the data, and go to the “Download” tab, select the downloaded file on disk and click on the “Load data” button:

This example is only suitable for transferring data between identical configurations on the 1C platform. To understand the exchange mechanism for programmers, we wrote an article -.

Probably every 1C specialist has encountered the need to transfer data from one information base to another. In the case where the configurations are different, you have to write data conversion rules. These rules are created in the 1C “Data Conversion” configuration.

Data can also be transferred using . Many 1C 8.3 configurations have standard functionality for setting up data synchronization between different configurations and seamless integration with 1C Document Flow.

But when data needs to be transferred between absolutely identical configurations, you can simplify your task and use standard processing for uploading and downloading via XML. Please note that this method, like data conversion, compares objects with each other by a unique identifier (GUID), and not by name.

You can download this processing on the ITS disk, or using the links:

It is universal and suitable for any configuration.

Let's consider an example of unloading the "Nomenclature" directory from one 1C 8.3 Accounting 3.0 information base to another. A prerequisite will be selection by the parent (group) “Woodworking”.

Uploading data from 1C to XML

Go to the information base from which the data will be downloaded (source). Be sure to check them, taking into account all possible conditions to avoid undesirable consequences.

Open XML data upload and download processing (Ctrl+O).

We are interested in the “Upload” tab. First of all, specify the name of the file into which the data will be uploaded and the path for saving. In this case, the data is uploaded “To a file on the server.”

In the processing header you can configure the period for which the selection will be carried out. Also, for periodic registers, you can specify the method of applying selection by period. If it is necessary to upload movements along with documents, the corresponding flag is set. In this case, we overload the directory, so there is no need to configure anything in the header.

Let's move on to selecting data for uploading. In the tabular part of the processing form, select the checkboxes for the configuration objects that you need to transfer.

The “Unload if necessary” column means whether it is necessary to overload this object if it is referenced by the attribute of the directory we are overloading. For example, the position of the item you are loading has a unit of measurement that is not in the target database. If the flag in the “Upload if necessary” column is checked opposite the reference book with units of measurement, a new position will be created. Otherwise, the value of the attribute will be “<Объект не найден>" and its unique identifier.

In a simple case without selections, the item overload setting will look like this.

In this example, you need to select only the items that are located in the “Woodworking” folder.

Similar processing for 8.2 allows you to set selections for each configuration object in a convenient form. In 8.3, unfortunately, there is no such functionality. One way out in this situation would be to select the necessary items on the “Additional objects for unloading” tab.

You can add objects here either manually (the “Add” button) or by request (“Add by request...”). If there are a large number of them, the second option is preferable.

In this case, the request will be as follows. Fill in the parameters, complete the request after checking the data, and click on the “Select result” button.

After you have specified all the necessary objects and additional elements for uploading, click on the “Upload data” button. They will end up in an XML file, the name and path of which you specified earlier. The results of this operation will be displayed in messages.

In this example, it was necessary to unload only 3 positions, but five were unloaded. This is because a flag was set opposite the “Nomenclature” directory in the “Upload if necessary” column. Along with the necessary positions, their parents were overloaded.

Loading a directory from XML

After successfully downloading data from the source configuration into an XML file, open the destination database. The structure of objects and their details must match each other. In this case, the transfer is carried out between two standard configurations 1C: Accounting 3.0.

Open processing in the receiver database. This processing is used for both uploading and loading data. Go to the “Download” tab and specify the path to the XML file into which the data was previously downloaded. After that, click on the “Download data” button.

The download result will be displayed in messages. In our case, everything went well.

The “Nomenclature” directory in the receiving database was not filled out. Now it has five elements: three nomenclature positions and two groups.

Very easy to use processing for quickly transferring data between identical configurations. Works via xml file or com connection.
Supports regular and managed forms. Runs on a web client.

Transfers data from one 1C database to another via xml file or com connection.

The configurations must be identical (in terms of data structure at least). For example, transfer something from a copy to a working database. The file is created in the processing folder. Transfers optional directories, documents (together with movements) and information registers. For periodic objects, you can set a period.

On the "Upload" tab there is a flag "Unload directories from documents". When uploading documents with the flag set, directories contained in the document details and tabular parts are uploaded along with their parents and owners (if necessary).

It can work in two modes: via xml (run one by one in the source database, then in the destination database), via com connection (run only in the source database).

In the com connection mode, it saves the connection settings to the server in the dataXML.ini file, the login and password are stored in encrypted form, and the rest of the data is in open form.

Even if the user does not take special actions to save the settings, the processing itself saves the data set in the dataXML.ini file. It stores: “Type of exchange”, “Download directories from documents” and connection parameters for com connections.

If the exchange operates in XML mode, the upload is made to the same directory from which processing is started. The file "dataXML.xml" is created. It is also loaded from there.

Usage (via xml):

• Start processing in the database - the data source. go to the "Upload" tab. If necessary, you can use the “filter by filled objects” flag - it will remove objects that do not contain data from the list fields, leaving only those with at least one record. Select objects to be transferred using the checkboxes (on any tabs)
• Click "Upload"
• Run the same processing in the database that receives the data. Select the type of exchange “Via XML”.
• Click "Download". The downloaded data will be displayed in a list, from where you can open it with a mouse click. The "Load Test" button on the "Loading" tab loads data without writing to the database and displays the downloaded data (if it is very scary to load).

Usage (via com):

• Start processing in the source database.
• Configure (restore settings) for the connection.
• Go to the "Upload" tab. If necessary, you can use the “filter by filled objects” flag - it will remove objects that do not contain data from the list fields, leaving only those with at least one record. Select objects to be transferred using the checkboxes (on any tabs)
• Click "Upload"

Updates:

2.4. Added selection by any object data when unloading. Selection is available only when uploading one type of directory or document. If the condition is met, the “Selection” tab appears on the “Unloading” tab.

Added a "file" field, available only when exchanging via xml. By default, "dataXML.xml" is filled in. This field is also added to the fields saved in the "dataXML.ini" file.

2.4.2. Added selection by organization. Set on the "Advanced" tab. The field is saved in the settings. If the selection is full, only those documents are uploaded that have the “Organization” attribute and the Organization of the document is equal to the selection.

2.5. On the "Upload" tab, the "Upload to list" button has been added. Becomes available if at least one type of document is selected for uploading. Designed for preliminary uploading of the result to a list on which you can check boxes on documents, as well as open the document form for viewing. Uploading from this form limits the list of uploaded documents to only those who have the checkbox selected.

2.5.3. I slightly changed the unloading of information registers (not fundamentally), detailed the messages when unloading information registers (deciphered the record selection). I split the problematic line from user its into two (to make the error easier to understand).

Renamed the other two flags (fitted into place). This did not change the essence of the flags; I hope the names are still clear. “Filled only” is a filter for all table parts, leaving for selection only those objects that contain at least one data object. "Documents with directories" - a flag that allows you to upload the directories contained in it along with the documents.

Part of the unloading has been slightly rewritten (slightly optimized).

When unloading directories contained in documents, a message has been added (previously they were unloaded “silently”).

2.5.5. Added user interrupt handling to upload and download.

2.5.6. Fixed a bug with types of information registers. Registers subordinate to the registrar have been removed from the "Information registers" field. If necessary, move them, move the recorders with movements.

2.7.4. Added new functionality (tab when uploading "According to exchange plan") Allows, if you have an exchange plan "Full", to upload (and download) data that is registered by the exchange plan.

Many different little things have been improved to improve the usability of the processing. Fixed errors when saving settings.

2.8.0. The wish of the respectednirbolz, made in the 251st comment, the "Only new" flag was added.

The configuration of the form has been slightly changed; the main flags have been placed on a separate tab, because the place on the form where they were before is gone :)

3.0.1. Added minimal functionality on managed forms. Exchange of directories, registers of information and documents (optional with movements).

Transferring various data is a very significant action in any accounting system on the 1C platform. Before exporting the directory to another database, it is necessary to make a backup copy, because the changes made are considered irreversible.

The most popular and at the same time fairly simple way to transfer a directory to 1C 8.3 is to process information data in XML form.

To perform this task, you will need to use the upload/download processing file for 8.2 or for 1C 8.3. This method is universal and the most optimal, suitable for almost any installed configuration.

Uploading data

To do this, you will first need to go to the program interface and perform a number of actions:

1. Fill in the “File name” field. Using this path, an information data file will subsequently be created for loading into the database.

2. In the “Data for downloading” table area, select the information from the directory that you want to download from the existing database.

3. After this, when the necessary objects are selected, apply a selection on the right side of the tables.

4. After completing the installation of all required settings, export the directory.

Loading data into the directory

To transfer directories to 1C, you will need to perform a number of actions:

1. Start processing in the database where you want to load information data, and use the “Load” tab.

2. Then select the previously uploaded file and use the “Load Data” command.

After completing this action, migration of the directory from one database to another is considered completely completed.

When maintaining several working 1C databases, sometimes there is a need to exchange data between them. There are 2 ways to transfer data:

Data transfer using the exchange and processing rules “XML Data Exchange”. Exchange rules are created using the 1C:Data Conversion configuration.

Transferring data between similar infobases using the “Uploading and loading XML data” processing.
Let's consider the second option, i.e. uploading and loading data from/to configurations that contain the same (identical) objects we need. To do this, we will use the external processing “Uploading and loading XML data”, which can be downloaded here.

The condition for using this processing is as follows: The information base from which data is downloaded must contain the same objects and with the same details (name and data type) as in the database into which the data is loaded.

Let's consider an example with data transfer using this processing. Suppose you need to transfer the documents “Incoming payment order” and “Outgoing payment order”. The solution to this problem will be as follows.

We open the external processing “Uploading and loading XML data” through the main menu: File? Open... On the “Upload” tab we specify the XML file into which we will save the data.

Then you need to specify the period for which we will unload data objects from the 1C database and the objects themselves. We mark the documents we need for uploading with a tick in the configuration object structure field in the “Data for uploading” column. If the uploaded documents contain links to directory elements that are not in another configuration, then it makes sense to check the boxes in the “If necessary” column so that these elements are also uploaded along with the documents.

Now at this step you need to decide whether to upload their movements along the registers along with the documents or transfer these documents to another database? To re-post uploaded documents in another database, you can use the “Group processing of directories and documents” processing. If the processing algorithms in these information databases differ in some way, then the checkbox next to “Upload all its movements with the document” should not be checked.

That's all, the upload setup is complete, everything is simple here! Click the “Upload data” button and wait until the data is saved to an XML file. For more complex unloadings, you can specify selection for unloaded objects not only by period.

After unloading, go to the second 1C database and open the same processing there. Go to the “Download” tab and indicate here the same XML file into which we uploaded the data.

On this tab, check the box next to “Continue loading objects if an error occurs” and click on the “Load data” button. We do not consider other functions, for example, the use of totals, although this function can significantly speed up the loading of objects (records by registers).