Transition from 1C Accounting 7.7. Options for switching to the latest generation ERP solution line configurations

Most users of the 1C 7.7 program imagine the transition from 1C 7.7 to 8.3 (8.2) as something complex and subject only to programmers. If the organization does not have a completely redesigned configuration, then this article was written for you and will help with the transition to 1C 8.3 or 8.2.

How to prepare a 1C 8.3 (8.2) database for subsequent data transfer from 1C 7.7 step by step

Before starting work, you need to prepare the 1C 8.3 (8.2) database for subsequent data loading.

Step 1

Update the 1C database to the latest release, use the latest version 8.2 or 8.3. You can check the relevance of the current release on the 1C technical support website.

How to install or update the 1C 8.3 platform, see our video tutorial:

Step 2

Carry out routine month-end closing operations. Additionally, you can check your accounting records via Service – Data verification for transition to 1C Accounting 8. If there are errors, correct them.

Step 3

Step 5

Create a clean database for loading data. This is necessary to promptly cancel the data download in case unforeseen situations arise. Select the top menu of the program Administration – Upload data, specify the name of the upload file and the location where it will be saved.

Thanks to these preparatory measures, unnecessary objects will be removed from the database, the 1C database will become smaller. The results will be recalculated and the logical integrity of the database will be checked. Now you can start transferring data from 1C 7.7 to 1C 8.3 (8.2).

How to add an information base in 1C 8.3, see the following video lesson:

Transferring data from 1C 7.7 to 1C 8.2 Accounting 2.0

In the latest version of the release of the 1C 8.2 Accounting 2.0 program, translation from 1C 7.7 information databases is not supported. In accordance with the requirements of the 1C company, it is necessary to do. Therefore, if in the 1C 8.2 database you select Service – Transfer of data from information databases 1C Enterprise 7.7, then we get the error:

But what should you do if you really need to transfer it specifically to version 1C 8.2?

Step 1. Uploading data from 1C 7.7

It is necessary to download files that were previously supplied by 1C for uploading to 1C 8.2 Accounting. These files must be placed in the ExtForms folder from your database. In the example, this is D:\1с\77\unp_demo\ExtForms. You can view the path to your database when loading the 1C program:

Let's run this processing: If everything is done correctly, the message “Uploading data for 1C Accounting 8” should appear, select it by clicking the Open button:

• Upload rules – a file named Acc77_80.xml, we copied it to the ExtForms folder;
• Start date and end date – the period during which the data will be downloaded;
• Rules for uploading data – objects to be uploaded, directories and documents that need to be uploaded to a file.

The data file in the example will be copied to the desktop, but you can select any other folder. Click the Load exchange rules button. A list of objects that will be unloaded from 1C 7.7 will open and which can be edited by removing or checking the selection boxes:

Depending on the situation, you can upload data either all at once or in parts. First, we unload the directories - 95% of them are unloaded without problems. With the second file we upload balances and turnover by accounting sections. This option is convenient to use if some data is not uploaded quite correctly.

Step 2. Loading into 1C 8.2 Accounting 2.0 from 1C 7.7

Choose Service – Transfer of data from information databases 1C Enterprise 8, in the window that appears, select Load from file:

Select the file that was downloaded from 1C 7.7 to the desktop. After clicking the Next button, data will be loaded from the file. If accounting in the 1C 7.7 database has been maintained for a long time, then loading may take a long time.

If errors occur during downloading, only part of the data will be downloaded and therefore will have to be downloaded again.

Transferring data from 1C 7.7 to 1C 8.3 Accounting 3.0

The algorithm for transferring a database from 1C 7.7 to 1C 8.3 is slightly different in detail, but in general it is similar to that described above for 1C 8.2 Accounting 2.0.

Step 1

After updating the 1C information base, it is necessary to update the data upload rules. This can be done as follows.

Open 1C 8.3 Accounting 3.0 and select the Save transfer rules button in the lower right corner, select version 1C Accounting 7.7 and save the rules by specifying the path to the ExtForms directory of the information database:

Step 2. Uploading data from 1C 7.7

The ability to upload from 1C 7.7 to 1C 8.3 is made by default, that is, there is no need to download additional files and add them to the database.

Let's start unloading processing: Service – Additional features. We find the inscription Transition to 1C 8.3 Accounting ed. 3.0 and click Open:

In the window that appears, you must fill in:

• Upload rules - a file named ACC_ACC8.xml, which can be found in the folder with your database (how to determine the path to the database was described above), the ExtForms folder. This is the one copied from 1C 8.3;
• Start date and end date – the period for which the data will be downloaded;
• Data file name – the place where we will copy the file with the uploaded data;
• Rules for uploading data – objects to be uploaded, directories and documents that will be uploaded to a file:

Click the Load exchange rules button. A list of objects that will be unloaded from 1C 7.7 will appear, which can be edited by removing or checking the selection boxes.

You can upload in parts, creating several files, or upload all the data at once. What to do depends on the specific situation. In the example, we upload all the data at once.

Let's open 1C Accounting 3.0 (8.3) and select Here we will see 2 ways to load data:

• Load data from an infobase - the 1C 8.3 program itself will find the installed databases and try to connect to this infobase, copying the data from there. Using the settings, you can specify what needs to be loaded and click the Load data button:

• Loading data from a file is just our option. You must specify the file that was downloaded from 1C 7.7 and click the Load data button. If a window like the one below appears, it means that the download was successful. Otherwise, you need to download either in parts and correct the errors that the program produces in 1C 7.7:

Transfer of data from the modified standard configuration of 1C 7.7 to 1C 8.3 (8.2)

Transferring data from changed 1C 7.7 configurations is much more complicated due to rewritten business processes that do not exist in the edition of the program to which we will transfer the data. In most cases, such transfers should be done by a specialist with experience in data transfer or good knowledge of Data Conversion configuration. There are general migration principles that can be used to migrate such configurations:

• Transfer of functionality. In the new configuration, it is necessary to repeat the functionality that is present in 1C 7.7. Additional documents, reference books and details. Unload -CF of this database.
• at the end of the year. Compare account turnover before convolutions and after- they must be equal.
• Transfer of data from a collapsed 1C 7.7 database to a standard clean database of the new edition. Check the turnover data on accounts in 1C 7.7 and 8.2 or 8.3. If there are errors, correct them.
• Into the clean database into which data was loaded from 1C 7.7, it is necessary to upload a CF configuration file in which the functionality from 1C 7.7 was repeated.
• Additional directory details can be transferred using the Data Conversion configuration.

Checking data after transferring data from 1C 7.7 to 1C 8.3 and 8.2

Using the Turnover Balance Sheet report, generate a report with data on subaccounts, accounting types, off-balance sheet accounts, currencies and compare with the same report from the 1C 8.3 (8.2) database into which the data was transferred:

Currently, the transition from 1C:Enterprise 7.7 to 8.3 (similar to 8.2) has become a headache for accountants. Preferably as quickly as possible and without errors. If you are a 1C:Accounting programmer and you need to convert documents from the seventh version to the eighth, then this article is for you.

Take just a few steps and your data transfer problems will be solved. Read this instruction to the end, and you will see how to do this. First, you must prepare a workplace on your computer for the necessary manipulations. Firstly, your hard drive must be at least 100 GB. This is necessary because it is multi-level. And you will need to work with several 7.7 configurations.

If you need a quick and high-quality transition from 1C Accounting 7.7 to 1C 8.3, contact us! Our average turnkey cost is 6,600 rubles.

Transferring data from 1C 7.7 to 1C 8.3 accounting 3.0

So, before working with transferring data to version 1C 8.3, you need to prepare this data in version 7.7. To do this you must do the following. Let’s say you have a working database “Accounting for an Enterprise” on your computer, which your accountants work with. Using Export77 processing, upload all the necessary documents to a text file and from that moment on, never return to the main working database. Your further manipulations will occur with other configurations.

Install the latest Release 1C:Enterprise 7.7 into the new directory. (the package includes a standard empty version (without data) and a demo version). We will work with the standard version. Now run this database and, using Import 77 processing, load data from your main database from a text file.

When converting data, some documents may not be processed. It's not scary. The trick is that you can easily fix this after the transfer, since in the standard database you work with the main standard chart of accounts. Therefore, no matter how sophisticated the subaccounts are, it is easy to fix this in your working database in about 3 hours by going into each unposted document and changing the accounts that you have in your configuration in the account fields.

Naturally, before the transfer, you first bring the chart of accounts of the standard configuration into line with the chart of accounts of your main working base. The options are purely individual depending on the specifics of your organization. Having done this work, you receive a standard configuration filled with data from your working database.

Now we need to do another data transfer. To do this, install the standard zero configuration again in a new directory. And transfer the data there from the standard configuration with your data. As a result, you will get an ideal version 7 database, ready for transfer to version 8.2.

The fact is that data is transferred directly to the eighth version exclusively from the “untouched” standard version 7.7. And now you have just such a configuration. But now it is not empty, but with your work data.

All! We launch 1C:Enterprise 8.2. Select “Data transfer from version 7.7.” and enjoy how the program itself transfers data from your processed 7.7., transfers documents and displays a comparative table of the balance sheet of versions 7.7 and 8.3.

Of course, there will not be a 100% result. But at 70-80 percent you will get a match. And then your work will be done only in version 8.3.

Possible inaccuracies are easily corrected. It's another 3-4 hours. You go to the document journal and either adjust accounts or fields (for example, “Agreement” or “Main cash desk”). It depends on the degree of difference between your 7.7 base. from standard. As a result of all these actions, your working configuration of version 8.3 will be able to produce accounting data through the balance sheet in an ideal form.

After the transition, it will be useful for you to learn how to work in the new program. For this we have prepared a section.

By the way! If you need modification of 1C programs, you can contact us!

Video on the transition from 1s 7.7 to 8:

It would not be an exaggeration to say that all users of 1C: Accounting 7.7 who have decided to switch to 1C: Accounting 8 are concerned about the issue of data transfer. And not just a mechanical transfer of directories, but a transfer of all the information accumulated in accounting and tax accounts, which would allow users to start working in the new program immediately after purchasing it. For a quick transition from “1C: Accounting 7.7” to “1C: Accounting 8”, a mechanism called “Transition Assistant” was developed. More precisely, two assistants. One is intended for downloading data from “1C: Accounting 7.7”, the second is for loading data into “1C: Accounting 8”. 1C methodologists talk about how to use the assistant.

Call Assistant in "1C: Accounting 7.7" can be done from the menu "Service - Transition to 1C: Accounting 8" (see Fig. 1).

Rice. 1

Working with the Assistant is divided into five steps. The transition from step to step is carried out using the “Next” and “Back” buttons.

The first step is getting to know each other. Here is a brief description of the purpose of the Assistant, you can view information about the advantages of "1C: Accounting 8", and indicate where you can get additional information about the transition to "1C: Accounting 8".

The second step provides the opportunity to check and, if necessary, obtain an update to the standard configuration. It is recommended to use the latest configuration release, as the program is constantly updated due to changes in legislation.

If there are no updates, you can continue working.

If there is an update, then you can get a new configuration release.

After receiving a new release, you should update the configuration. To do this, you will need to exit the Assistant and close the program. After updating the configuration, the Assistant will be launched automatically to continue the transition, and will offer you the next step.

The third step requires you to indicate what information needs to be transferred. You can only transfer balances from accounting and tax accounts to the beginning of the year.

Or balances at the beginning of the year and turnover from the beginning of the year to the end of any month.

Particular attention should be paid to the fact that before making the transition, it is necessary to carry out routine month-end closing procedures in each month that is included in the unloading period.

At the fourth step, the Assistant indicates which file the uploaded data will be written to. If you do not change the default settings, then when loading data into 1C: Accounting 8, the Transition Assistant to 1C: Accounting 8 will find the specified file automatically.

And finally, the final step is downloading the data. If you check the “Generate balance sheet” checkbox, then after uploading a balance sheet will be generated, which can be printed and with which you can compare the result of loading into “1C: Accounting 8”. Directly unloading is carried out by clicking the "Unload" button.

This completes the work of the Migration Assistant from "1C: Accounting 7.7".

Now you need to run "1C:Accounting 8" and start downloading data.

You can call the Assistant from the menu "Service - Transition from 1C: Accounting 7.7" (see Fig. 2).

Rice. 2

Just like in 1C: Accounting 7.7, working with the Assistant is divided into several steps. The transition from step to step is carried out using the “Next” and “Back” buttons.

The first step is getting to know each other. Here is a brief description of the purpose of the Assistant, it is indicated where you can get additional information about the transition to "1C: Accounting 8", there is a hint on what needed to be done to download data from "1C: Accounting 7.7".

The second step provides the opportunity to check and, if necessary, obtain an update to the standard configuration. It is recommended to use the latest configuration release, as the program is constantly updated due to changes in legislation. After receiving a new release, you should update the configuration. To do this, you will need to exit the Assistant and close the program. After updating the configuration, the Assistant will be launched automatically to continue the transition, and will offer you the next step.

Information about the organization will have to be filled out only by users of the basic version of 1C: Accounting 8. Please note that the TIN and KPP must completely match the TIN and KPP entered in “1C: Accounting 7.7”. In "1C: Accounting 8 PROF" the organization will be created automatically when loading data, and the Assistant will skip this step.

Before you start loading data, you need to set up inventory accounting. The fact is that in "1C: Accounting 7.7" only quantitative accounting is supported by warehouses. In "1C: Accounting 8" the possibilities of warehouse accounting are much wider: you can keep batch accounting, you can keep quantitative and total accounting for warehouses, or you can turn off warehouse accounting. If the warehouse accounting settings do not correspond to the functionality of "1C: Accounting 7.7" (warehouse accounting is disabled), the user is prompted to install warehouse accounting. If inventory management has already been enabled previously, the Assistant will skip this step.

The next step is to specify which file the data should be loaded from. The Assistant automatically searches for the file with the uploaded data by the name that was specified by default in the Assistant when uploading data from "1C: Accounting 7.7".

And finally, the final step is loading the data. Direct downloading is carried out by clicking the "Download" button.

If you check the "Generate balance sheets" checkbox, then after loading a turnover balance sheet for accounting accounts and a balance sheet for tax accounting accounts will be generated, which can be printed, with which you can check the balance sheet generated during downloading data from "1C: Accounting 7.7".

Before you start working with the 1C: Accounting 8 program, you need to set the basic accounting parameters:

• set up accounting policies;
• set up tax accounting policies;
• set up analytical accounting of inventories;
• set user settings, etc.

Check the "Open Start Assistant" box in the transition assistant from "1C: Accounting 7.7", and after loading the data, the Start Assistant will launch automatically.

This completes the process of transition from "1C: Accounting 7.7" to "1C: Accounting 8".

Many users of 1C: Accounting 7.7 who have decided to switch to 1C: Accounting 8 are concerned about the issue of data transfer. For a quick and accurate transition, a mechanism was developed called the “Transition Assistant”.

You can call the Assistant in "1C: Accounting 7.7" as follows: "Service - Transition to 1C: Accounting 8" (see Fig. 1).

Working with the Assistant is divided into five main steps. The transition from step to step is carried out using the “Next” and “Back” buttons.

The first step is getting to know each other. Here you can read a brief description of the purpose of the Assistant, the advantages of "1C: Accounting 8", and see where you can get additional information about the transition to "1C: Accounting 8".

In the second step, you are given the opportunity to check and, if necessary, download an update to the standard configuration.

In the third step, you need to specify what information you want to transfer. You can only transfer balances from accounting and tax accounts compiled at the beginning of the year.

Step four. The assistant indicates which file the uploaded data will be written to. If you do not change the default settings, the Assistant will find the specified file automatically.

And finally, the fifth step is downloading data. If you check the "Generate balance sheet" checkbox, then at the end of the unloading a balance sheet will be generated. The upload itself is usually carried out by clicking the "Unload" button.

At this stage, the work of the Migration Assistant from "1C: Accounting 7.7" is completed.

Now we need to launch “1C: Accounting 8” and start loading data in this program.

The assistant is called as follows: "Service - Transition from 1C: Accounting 7.7".

Just like in "1C: Accounting 7.7", work with the Assistant is divided into separate stages. The transition from stage to stage occurs using the “Next” and “Back” buttons.

Step one is getting to know each other. Here we briefly describe the purposes of the Assistant and indicate where you can get additional information about the transition to "1C: Accounting 8".

The second stage provides the opportunity to check and, if necessary, obtain an update to the standard configuration. After receiving a new release, you need to update the configuration. To do this, you will need to close the program. After updating the configuration, the Assistant will be launched automatically to continue the transition, and will offer you the next step.

Information about the organization must be filled out only for users of the basic version of 1C:Accounting 8. The TIN and KPP must match the TIN and KPP entered in "1C: Accounting 7.7".

Before loading data, you need to set up warehouse accounting. In "1C: Accounting 7.7" only quantitative accounting is supported by warehouses. In "1C: Accounting 8" the possibilities of warehouse accounting are much wider. In the event that the warehouse accounting settings do not correspond to the functionality of "1C: Accounting 7.7", the user can install warehouse accounting. If inventory accounting has already been enabled previously, the Assistant will skip this step.

Next, you should indicate which file you want to load the data from. The Assistant will automatically search for the file with the uploaded data by the name that was specified in the Assistant when uploading data from "1C: Accounting 7.7".

And now, the final step is loading the data. Downloading is carried out by clicking the "Download" button.

Before starting work in the 1C:Accounting 8 program, you need to set the basic accounting parameters:

• set up accounting policies;
• set up tax accounting policies;
• set up analytical accounting of inventories;
• set user settings, etc.

If you are reading this article, it means that you have probably already answered this question in the affirmative. Therefore, now we will not talk again about the advantages of switching to a new platform, but will focus directly on the details and features of this process.

1. General algorithm

Rice. 1. Algorithm for transition from the 1C:Enterprise 7.7 platform to the 1C:Enterprise 8.2 platform

1. Upgrade. The first thing you need to do is write an application from your organization, submit a registration form for platform 7.7 and purchase platform 8.2. In this case you will be provided discount in the amount of the cost of the old platform, but no more than 50%. The old platform remains with you, and you can continue to use it, however, it will be removed from technical support at 1C.

2. Update current configuration until the latest current release.

3. Preparing the database for transfer. This involves backing up the database, closing the current billing period, clearing the database of items marked for deletion, and correcting accounting errors (if any).

4. Data transfer. This is the main stage. Algorithms and labor intensity are different in each specific case.

5. Training of personnel to work with the new configuration. Since the configurations on platforms 7.7 and 8.2 differ both in interface and functionality, you may need training to work with the new configuration. You can study it yourself using the appropriate methodological literature, but it is better to take a specialized course.

6. Operation. At this stage, when users start working in the new program, it is debugged and possible errors in automated data transfer are corrected.

Let's consider the process of migrating to a new platform in the context of configuration "1c accounting".

2. Change “1C: Accounting 7.7” to “1C: Accounting 8.2”

• start time of accounting in the new program;
• the presence and complexity of modifications in the current version of your configuration;
• the need to preserve the history of business transactions for past periods.

Depending on the combination of the above factors, situations may be as follows.

Situation 1:

Transition from the new year, TYPICAL configuration, correct account balances are generated in the old program

This option is simple and clear, but in practice it is extremely rare. It is only possible in a number of small companies to generate correct balances in the old program immediately before starting work in the new program, and only on the condition that all primary documents for the past period are provided and entered into the program.

If this is your case, you're in luck. You only need to update the “1C:Enterprise 7.7” configuration to the latest version and use the “Transfer of data from 1C:Enterprise 7.7 information bases” processing built into “1C:Enterprise 8.2”. You can do this yourself, without the help of a specialist. You just need to strictly follow the instructions specified in the processing.

Situation 2:

Transition from the new year, TYPICAL configuration, in the old program there are NO CORRECT ACCOUNT BALANCES

The standard practice in this case is working in the old and new program simultaneously . During the “transition period” (Fig. 2), employees close their previous transactions in the old program and begin to enter documents on new transactions into the new system.

Rice. 2. Transition period when changing platforms

To overcome this period with minimal losses, you can use the following strategies:

• transfer balances “as is” to the beginning of the year and keep records based on this data. Once the correct balances in the "seven" are obtained, they must be immediately adjusted retroactively in the "eight".
• refuse to transfer incorrect balances and enter primary documents for new transactions into the G8 without subsequently conducting them. In this case, it doesn’t matter whether there are balances in the program or not; unposted documents will not make any movements on the accounts. This must be done until the correct balances are received in 1C:Enterprise 7.7. Next, the resulting balances are transferred to the new program at the beginning of the year. The final step is the consistent implementation of the “primary” introduced into the new program during the transition period using built-in processing “Group processing of directories and documents” .

“1C: Accounting 8.2” supports a number of mechanisms important for accounting, the performance of which depends on the data entered into documents during the year. Among such mechanisms are the already mentioned calculation of taxes on an accrual basis, an algorithm for the distribution of indirect expenses and other procedures related to the closing of the month. It is precisely because of these features that in this situation it is impossible to switch to a new program as easily as in the first two cases. To minimize the number of errors that may occur during migration, we recommend:

• start work, if not from the beginning of the year, then at least from the beginning of the quarter;
• transfer balances to the beginning of the year;
• transfer all primary documents for the current reporting period (year) to the new system and restore accounting and tax data using group processing of directories and documents.

• Standard solution "1C: Data Conversion 2.1". This software product can be used to transfer information between configurations on the 1C platform of any structure and complexity.
• Developments of 1C franchisees. Many companies, including RG-Soft, have proven methods for solving this problem, which can significantly reduce the time and budget of data transfer work.

Separately, we note that there are companies that maintain long-term (more than a year) relationships under contracts with counterparties. The management of such companies is interested in having a history of business transactions in the program. The presence in the new program of documents entered in the old program allows users to easily and quickly track relationships under specific agreements/transactions.

It is possible to implement such a transfer using the same mechanisms as in the previous situation. The difference between this process is that there is no need to transfer all documents; you can limit yourself to transferring only a few types of documents, and the balances for other accounts are entered through standard processing. In this case, additional transferred documents are usually left unposted.

Although it is possible to transfer documents for the past period from an old program to a new one, such a transfer leads to a noticeable increase in the size of the database, and, consequently, the size of the processed tables. This may cause the system to slow down. Therefore, you should not use this transition option unless absolutely necessary. It is recommended to leave documents transferred from previous periods unposted so that the information they contain does not affect current accounting and tax reporting. Use historical documents for reference purposes only.

Situation 5: Transition from a NON-TYPICAL configuration on the 1C:Enterprise 7.7 platform

The options described above are used when migrating from the standard “1C:Enterprise 7.7” configuration, but in practice you often have to deal with modified configurations. Organizing a transition in this situation is a special option that deserves consideration.

Depending on the nature of the changes made to the program, the following data transfer technologies are available:

• if the configuration has been changed slightly and the basic mechanisms are similar to the standard 1C solution, you can, as in the previous options, use standard transition tools. You only need to configure or slightly modify them to suit your program. Perhaps the most tested and reliable tool is the already mentioned “1C: Data Conversion 2.1”. This tool will require certain operating skills from the user, but with its help it is possible to organize automated transfer of objects between configurations.
• if over the years of use the configuration has been radically redesigned, then setting up standard migration tools may turn out to be more labor-intensive than writing your own processing for these purposes. A similar situation arises in the case of organizing a transition from an accounting program that is not associated with 1C platforms. It is also possible to make such a transition, but it will not be possible to come up with a universal exchange in advance. Each specific case requires an individual approach to the problem. Our company can offer its developments for transferring data through files of various formats, such as dbf, xls, xml.

Due to the lack of a mechanism for maintaining records of several companies in one database, many enterprises had to maintain several databases simultaneously in 1C:Enterprise 7.7. Since this problem has been solved in the eighth version, the task arises of combining several databases into one as part of a data transfer project. Moreover, each of the seven bases can have its own characteristics.

Using the methods given above, you can establish interaction with each of the databases separately. However, a number of subtasks arise that are specific to this case.

• Unification of documents related to a particular organization. This problem is easily solved using the prefix mechanism. Each organization registered in the program is assigned its own letter prefix. This prefix is ​​added to the document number, thereby ensuring the uniqueness of the numbers.
• Control of duplicate elements of directories. When transferring data from several information sources to a single information system, a situation may arise when the same elements of directories, for example, the same counterparty in a new directory will be repeated several times. Therefore, after transferring data, it is necessary to perform a procedure for comparing and merging duplicate directory elements.

3. Possible difficulties that you should be aware of

3.1. Errors in source data

In general, unambiguous identification of an object in the database is possible using the TIN and KPP details. In the seven, both of these values ​​were stored in one TIN/KPP detail, and there were no checks for the correctness of the data entered into this detail. It was possible to enter fewer numbers, put the separator in the wrong place, and enter a completely abstract TIN.

A typical transfer, when creating a directory, counterparties are separated by TIN and KPP by simply cutting off the required number of characters. Therefore, absolutely incorrect data may be recorded in the details of the new database. Thus, correct identification of objects during transfer using such data will be very difficult.

Another problem is the lack of a unified data entry format. Each user can enter the name as he or she likes best. Let’s imagine that in one “seven” database the user, filling out the “Name” of the counterparty, wrote “Vympel Management Company”, and in another “seven” database the same counterparty is listed as “Vympel Management Company”. In such a situation, automatic processing will not be able to determine that this is the same counterparty, and will move it to the eight twice. It will be difficult to work further in such a database, since part of the balance will be on one element, and the second part on another.

3.2. Configuration differences

Another group of transfer errors is caused by technological differences in configurations. Some business transactions are reflected in “1C:Enterprise 7.7” by several types of documents, and in “1C:Enterprise 8” by one. For example, receipts of both materials and goods are reflected in the new program with one document, and in the old one - with two. Thus, when trying to transfer the documents “Receipt of materials No. 22” and “Receipt of goods No. 22”, a uniqueness control error occurs. Since recording two documents with the same number in a given period is impossible, it is necessary to artificially introduce differences into them and the system for introducing these differences is agreed upon in advance.

For example, this problem is solved by adding an additional prefix to the number of the downloaded document. For each feature of the document, this prefix is ​​allocated separately. This may be a characteristic of the database from which documents are downloaded or the type of document from which the download was made. Here is an example of the formation of such a prefix. The branch base in Krasnoyarsk gives the prefix “KR”. The document type “Receipt of materials” from which the download is made is given the prefix “M”. So, if the document number in seven was 00000031, then the eight number will be as follows:

“KR” + “M” + “00000031” = “KRM00000031”

As a result, a unique number will be recorded in the database.

3.3. Technical problems

Data transfer errors may also occur due to technical features of the 1C:Enterprise platform. For example, the standard search mechanism by name does not distinguish capital letters in the name of a directory element from small ones. There is confusion when using this mechanism. For example, in the database there are two counterparties “l-audio” and “L-Audio”. When searching for an “l-audio” counterparty, the system will find “L-Audio”. The result will be an incorrectly completed document.

It is also necessary to pay attention to the chosen data transfer method itself. The example described above with doubling of counterparties, when transferred from the databases of company branches, may not actually turn out to be doubling. Companies operating in different cities may well have counterparties also operating in different cities. The branch of the L-Audio company in Nizhny Novgorod and the L-Audio company itself in Moscow can rightfully be called exactly the same in the databases. To avoid such confusion, you need to choose a transfer method in advance. In our example, we can separate counterparties into different directory groups depending on the source database. The choice of such a technique will also affect the data loading mechanisms.

The methods described above for solving emerging problems may also not be universal enough. When migrating data, it is very important to be able to combine the methods used in the migration tool. For example, we identify most elements of directories by name. At the same time, when transferring the document “Acceptance of fixed assets for accounting,” this method will give undesirable results in the case when a number of small fixed assets of the same type are entered (office supplies, furniture, etc.), differing only in the inventory number. Each document of acceptance for accounting will indicate the same object. And accepting one object for accounting several times is impossible. Therefore, it is very important to provide the ability to customize the data migration tool used. In this case, we will simply indicate that the search for the OS must be carried out by the accession number (code).

Conclusion