1c transfer from 7.7 to 8.3 accounting. Additional differences from standard rules

For correct migration, it is advisable to update the source configuration and the destination configuration to latest version... At the time of this writing, these were

• 7.70.544 for the source;
• 2.0.42.6 for the receiver.

Choice of processing and data transfer rules

Data transfer from 7.7 should be performed by appropriate processing and according to the rules that should be selected in 8.2 from the reference book “Conversions from infobases of previous generations” (see Fig. 1):

Rice. 1. Selection of processing and rules from the reference book “Conversions from infobases of previous generations”.

Let's save the selected processing and conversion rules. In the future, if necessary, they can be edited in the "Data Conversion 2.1" configuration and will be used for data transfer.

Editing in the "Data Conversion 2.1" configuration

If the source database is standard, there is no need to use the "Data Conversion 2.1" configuration, and you can immediately proceed to the next step. For modified databases, or to change the standard rules for transferring to the conversion database, you should load the saved rules (Fig. 2):

Rice. 2. Uploading exchange rules

After the rules are loaded, you can edit them to suit your migration requirements. For example, the customer has set the task to transfer the “Materials” directory with the original source codes. In the standard rules, the search for elements of the Materials catalog is performed by three attributes (ThisGroup, Name, Parent), search by code is disabled and, in addition, in the rule for converting code properties, its length is reduced to the standard for 8.2. length padded with leading zeros on the left (Figure 3). Note that even if you use the standard rules, but with the value of the "Unload directory codes" parameter, then everywhere for the corresponding rules "Before unloading" you will still have to replace the text "Parameters.UploadCodes = Yes" with the correct expression "Parameters.UploadCodes = 1" , so you have to use the "Data Conversion 2.1" configuration or edit the code manually directly in the processing of Exp77_82.ert.

Rice. 3. Standard transfer rules for the "Materials" lookup code

Now we will change the transfer rules so that the items of the “Materials” catalog from 7.7 are transferred to 8.2. with original source codes. To do this, firstly, we will set the search by the attributes Code, ThisGroup, and remove the code conversion rule that has become unnecessary. Secondly, let's add a few lines to the “Data exchange rules” for our conversion in order to make a preliminary setting of the transfer parameter, according to which the directory codes will be unloaded from the source database (Fig. 4):

If ParameterSettingsTable.FindValue ("UnloadCodes", NS, "Name") = 1 Then

ParameterSettings Table.SetValue (НС, "Value", 1)

EndIf;

You don't need to do this setting, but then every time you call processing data upload from 7.7 on the “Parameters” tab it will be necessary to set the “Unload directory codes” parameter to the value 1.

Rice. 4. Setting transfer parameters

It is important to remember that the performed settings must not only be saved in the unloading rules, but also the processing module 7.7 Exp77_82.ert must be replaced with the one obtained from the data conversion (Fig. 5).

Rice. 5. Saving the exchange rules

To unload data from 7.7, we will call the appropriate transfer processing, indicate in it the data transfer rules (Acc77_82.xml) and the file where the transfer result will be saved (Spb_buh_77_82.xml), as well as the “Start date” and “End date” details. In this case, balances by accounting sections will be transferred to the start date, and the transfer of documents will be performed for the period from the start date to the end date. If you want to transfer complete information, you can select all data transfer rules. But, as a rule, only the selected "Balances by accounting sections" are transferred, while directories and documents referenced by these accounting sections are transferred automatically. This greatly reduces the transfer time.

Rice. 6. Uploading information

Next, we will call the appropriate form from the Service -> Organization Information menu, switch the keyboard case to Russian, and copy the name of the organization to the clipboard. It is mandatory to switch the case, otherwise the information in the clipboard will be incorrect for copying in 8.2.

Rice. 7. Information about the organization

Loading information in 8.2

Let's call the processing “Assistant for entering information about the organization” and replace the name “Our organization” with the name copied to the clipboard from 7.7. (fig. 8.)

Rice. 8. General information about the organization

Let's copy the TIN and KPP details from the corresponding fields “Information about the organization” on the “Codes” tab. When transferring data, the organization will be identified by them. You do not need to copy other details, since they will be filled in during the exchange. Let's save the entered information.

Now let's execute the menu item Tools -> Transfer data from infobases 1C: Enterprise 7.7 and select the item “Load data from file”. In the form that opens, indicate the location of the file and click the "Next" button.

Everything! The download result can be seen in the activity log.

Principle of operation.

A few words about how data is transferred from a typical configuration " Accounting", Edition 4.5 for 1C: Enterprise 7.7 or configuration" "(hereinafter referred to as Configuration-source) into a typical configuration" Enterprise accounting", Revision 3.0 for 1C: Enterprise 8 (version 3.0.52), hereinafter referred to as" Configuration-recipient ".

IMPORTANT! Data transfer is possible from configuration Accounting edition 4.5 for 1C: Enterprise 7.7 versions 7.70.569 and later or from configuration " Simplified taxation system, ed. 1.3"versions 7.70.219 and higher.

It is recommended to switch from the source configuration to the receiving configuration at the beginning of a new period (year, quarter, month) after the completion of the scheduled operations of the previous period.

Data transfer is performed using specialized processing that unloads data from the infobase of the Source Configuration to a file in XML format... The resulting file is loaded into the infobase of the recipient Configuration using universal processing loading data.

The following files are required to transfer data:

ACC_ACC8 .ert - external processing of unloading data into external file from the configuration " Accounting, rev. 4.5»;

USN_ACC8 .ert - external processing of unloading data to an external file from the " Simplified taxation system, ed. 1.3»;

ACC_ACC8 .xml - data conversion rules.

USN_ACC8 .xml - data conversion rules.

Portable data.

The following are transferred from the infobase Source configurations to the recipient configurations:

Elements of directories;

Information about the current balances on the accounts of the infobase of the Configuration-source as of the date of conversion of the infobase;

Current documents with a date greater than the infobase conversion date.

Conversion is performed in two stages:

Data from the Source Configuration infobase are uploaded to a separate file (data file);

The resulting file is loaded into the information base of the recipient Configuration.

Installation.

Use setup.exe to install migration processing. After starting the program (if the number of 1C: Enterprise infobases is large, then after a while) a dialog box will appear in which you need to select those infobases where data transfer processing will be installed. The window looks like in Fig. 1. If the number of infobases is more than seven, then use the "up" and "down" buttons to navigate. If several infobases are selected, then the "path" line reflects the location of only the last selected base. This information is of an auxiliary nature and is used optionally for additional control by the user over the result of work. installer, do not pay special attention to it, the program will itself determine where the information bases you have selected are installed.

Fig. 1 The infobase selection window during installation

Additionally, you can specify the folder into which the data transfer processing will also be installed; for this, use the folder selection window (by clicking the button with three dots). The full path for the selected folder will be displayed in the selection bar. After clicking on the "install" button, the installation will be performed required files to the selected infobases and / or to the selected folder. When finished, you can click the "details" button and see a detailed installation log, which files and in which folders were recorded. As a result, the following picture should appear in the selected folder, see Fig. 2.

Fig. 2 Files installed in the selected folder

To subdirectory ExtForms processing is set Transition to 1C: Accounting 8, ed. 3.0 and transfer rules. Please note that upload processing ACC_ACC8 .ert and data offloading rules replace typical processing and rules. If you want to keep the typical transition mechanism, install the new processing in a separate directory, and not in the infobase.

The installation process is described in more detail using the example of installing a report " for the configuration "1C: Accounting 7.7".

Operating procedure.

In a programme " 1C: Accounting 7.7"must be opened from additional opportunities processing " Transition to 1C: Accounting 8, ed. 3.0", select the folder containing the transfer rules (see Fig. 3) and load the exchange rules. You do not need to include all transfer rules. You should only use those that are necessary, for example, to transfer balances, or balances and documents. For example, in the reference books group not a single rule can be included, because all directories are moved by links as needed, that is, only those that are involved either in the remains or in the documents. This ensures that there is no "garbage" in the new information base... Documents do not need to include everything either. For example, if there are no documents in your database, or you do not want to transfer them, you do not need to enable this rule.

Fig. 3. Data upload processing

I recommend setting the name of the data file to "C: \ v77_v8 \ Exp77_80.xml", this folder is often used by default in the program " 1C: Accounting 8"when loading data from programs on the platform" 1C: Enterprise 7.7". If necessary, set the parameters on the" Options".

In the process of unloading data from the configuration " Accounting 7.7»May meet various errors... The migration rules presented here differ from the typical ones in that they search for typical errors at the data upload stage. Let's consider those of them about which messages are displayed.

Zero quantity and non-zero amount of goods and materials... It is impossible to enter the balance in the Receiver Configuration so that the quantity of the material is equal to zero, and the cost estimate of the material is not equal to zero, is impossible, and even meaningless, because this is an error. Therefore, when transferring balances, such items (with a zero quantity) will not appear in the balance entry documents. Therefore, if the errors are not corrected before the data transfer, then the amounts in the data source and the data receiver during the transfer of balances will not coincide, which will cause additional difficulties in reconciliation. Therefore, in the process of unloading data from the configuration " Accounting 7.7»Messages about encountered errors are displayed (see Fig. 4). Additionally, to search for errors, you can recommend using the "Express check of accounting" processing, namely the rule "No non-zero sum with zero quantity by materials".

Fig. 4.1 Error messages

Non-zero balance on the second (third) level subconto, while the balance at the first (second) level is zero. This is a fairly common situation of erroneous accounting. A typical example is shown in Figure 4.2. This condition arises as a result of "misgrading" in analytical accounting. For example, in the cash flow documents the contract is indicated, but there is no contract in the capitalization documents of goods and materials, or vice versa, or there are contracts but different. In all these cases, there is a non-zero contract balance, while the counterparty balance is zero. A similar picture can develop in accounting for materials and items (when total accounting by storage locations is included): re-grading between warehouses, especially if warehouses are materially responsible persons.

Figure 4.2 Example of accounting errors

It is clear that this is a mistake and it is clear that it does not make sense to carry over such leftovers. In order to exclude the transfer of this kind of balances, there is a parameter "Do not unload balances if there is a zero balance on upper level". If this parameter is set to one, then the messages shown in Fig. 4.3 (compare with Fig. 4.2) will be displayed during unloading, and the balances for such positions will not be unloaded. You can use various combinations of this parameter with the rules for transferring different residues. If you transfer not all balances at once, but according to accounting sections, then you can transfer balances for different accounting sections with different parameter values.

Figure 4.3. Error messages

Empty values ​​of contracts or other people's contracts. The problem is similar to the one described above, the reason is the same - misgrading in analytical accounting under contracts (see Figure 4.4). But the counterparty balance is not zero, so the above check rule will not work. When transferring data, an error will occur when posting the balance entry document, because an empty contract value is not allowed.

Fig 4.4 Report showing error

To exclude such errors before the transfer, at the stage of data uploading, error messages are displayed (see Fig. 4.5). The same figure shows that another error was encountered: the contract does not correspond to the counterparty, i.e. the owner of the contract is another counterparty. Such errors are often found in modified, i.e. atypical configurations or in long-established databases, when in typical configurations there was not a sufficiently strict check for compliance with contracts when filling out documents.

Figure 4.5 Accounting error messages

Checking for empty values ​​of contracts and other people's contracts is performed if the parameter " Check contracts for empty value and compliance with counterparty". Additionally, to search for errors, you can recommend using the" Express check of accounting "processing, namely the rules" No unfilled analytics for contracts "and" Compliance of contractors and contracts ".

There are other error checks, for clarification, contact us (contacts at the bottom of the page).

How to work

We will show how you can transfer data in parts, and not entirely, using the example of unloading documents of a particular type or even individual copies of documents of a selected type. Let's mark only one rule of data unloading " Payment order"(see Fig. 5). This will allow you to upload only documents of the" Payment order". If with such parameters you press the button" Unload", then all documents of the form" Payment order"located in the time interval with" start date" on " expiration date". Press the button" Install LDPE", after that the inscription" Selection of data for Payment order".

Fig. 5 How to set a rule for uploading data of a certain type

Then press the "Add condition" button, you will be able to select the selection attribute (see Fig. 6.1), most often it is - " CurrentDocument", which allows you to select a separate document from the list of documents of this type. You can, using other selection details, get a selection by a group of documents, for example, select documents by date. In all cases, documents are selected within the time interval specified by the parameters" Start date" and " expiration date".

Figure 6.1 How to select an individual document

Important! "1C"), which in some configurations does not allow the selection of documents when unloading according to the selection details. This is due to the fact that in model rules selection of documents is made by request without specifying the period. Such queries do not always work.

In a similar way, you can unload directories, not the entire directory, but by performing a selection by some attribute. First, select the required rule for uploading data, then sequentially press the buttons " Install LDPE" and " Add condition". For example, Fig. 6.2 shows how you can unload only those employees with whom at the time of transition from the program" 1C: Simplified taxation system, ed. 1.3" on " 1C: Enterprise Accounting, revision 3.0"(or, as users often say, the transition from accounting 7.7 to 3.0), an employment relationship has been established.

Fig. 6.2 How to select a group of directory elements

Important! In the proposed rules for data transfer, an error in the standard rules (from the company "1C"), which leads to an incorrect selection of directory elements when unloading according to the directory's periodic requisites, i.e. those that have different values ​​for different dates. This is due to the fact that, in the standard rules, the selection of directory elements is made by a query without specifying a period.

The selection by the periodic requisites of the directory is made on the date of the parameter " expiration date"!!!

You can use a combination of data unloading rules and filters. The rules for which the selection is set will be marked as "[SELECTION]". In order to see or edit the selection of a specific data unloading rule, you need to double-click on this rule in the list of rules or, by selecting it, press the " Install LDPE".

Important! If the unloading of objects turns out to be empty or incomplete, you need to check whether the synchronization mode with 1C: Accounting 8 is set. If so, then only the objects changed after the performed transfer will be unloaded (Directory.Parameters of SynchronousAccounting stores the Position of the LastDownloadedDocument, which is checked when unloading by the CheckForDownload function) ... Full work in synchronization mode becomes impossible. The synchronization mode is checked after loading the exchange rules. If the mode is set, a warning window will be generated (see Figure 6.5) and it will be offered to disable the synchronization mode.

Rice. 6.5 Sync Mode Warning Window

Additional differences from standard rules

The error of transferring IT&M with old receipt types has been fixed: if in the Goods and Services Receipt documents the receipt type is equal to 2 (outdated value) and there is no supplier invoice, an erroneous conversion of this document into BP 3.0 into the return document from the buyer occurs.

Fixed a bug when transferring manual operations that have a subdivision subdivision to the BP PROF version. Such an operation is not recorded in the BP, an error occurs: "The OU field must be empty." This is due to the fact that the rules are designed to work with versions of the CORP, however, in the TRAC, the dimensions DepartmentDt and DepartmentKt of the accounting register must be empty.

Fixed a bug leading to duplicate directory groups Contracts and, as a consequence, to duplication of the elements of this directory (since the search at loading is performed taking into account the parent). This is illustrated in Figure 6.6.

Fig. 6.6 Result of directory transfer Contracts model rules

Here in the column Parent(directory group) with the name 2015 there are two different groups reference book with the same name (there is only one group in the source), therefore the contracts are duplicated.

Fixed the error of transferring bank documents when transferring money from one current account to another. V BP 3.0 in this case a document is created Write-off from the current account with the type of operation Transfer to another account of the organization, which is not carried out due to the fact that the requisite is not filled Beneficiary account... In addition, the details are filled in incorrectly. Accounting account and Debit account... This will manifest itself if they are different, for example 55 and 51, then they need to be swapped. Fixed the error of not filling in the props Obligation type in the documents for the transfer of taxes. All of the above applies to the 3.0.43.215 release.

Props are transferred main contract handbook Contractors.

The rule of unloading the directory has been changed Nomenclature, now the data selection method is a standard selection, which allows you to select the elements of the reference book by details (in the standard rules of the USN 7.7 - BP 3.0 this is impossible). When transferring a directory Nomenclature, are carried over and Item prices by links, i.e. prices of only transferred item items. To enable this feature, you need to set the parameter value to one Unload prices when unloading an item.

Fixed an error in the standard rules "USN 7.7 - BP 3.0" when transferring balances for settlements with counterparties: the type of contract was always set to Other... Now - depending on the type of balance, according to the accounting section " Calculations with Suppliers and Contractors"type of contract =" Supplier", according to the accounting section" Settlements with buyers and customers"type of contract =" With the buyer", in other cases, the type of contract =" Other".

Fixed an error in the standard rules "USN 7.7 - BP 3.0" when transferring balances for settlements with counterparties: the amount of mutual settlements was recorded in two details of the initial balances entry document Sum and AmountKt... Because of this, the document for entering the initial balances was not posted.

CheckWith the buyer"(in standard rules" Other"). The value of the" Payment State", this is important for the right choice invoices for payment to the customer in bank payment documents in the recipient configuration.

When transferring documents of the type " Payment order"type of contract is set to" With the supplier"(in standard rules" Other").

Fixed an error in the standard rules "USN 7.7 - BP 3.0" when transferring storage locations: the requisite is not filled in " Warehouse type".

Added parameter " Exchange with regulatory authorities included": if its value is 1, then the props Kind of ExchangeControlling Bodies catalog item " The organization"set to value" Exchange in Universal Format"otherwise in" ExchangeDisabled"as in the standard rules. This is important for repeated (regular) transfers, so as not to spoil the EDF settings.

Changed rule for searching loaded items for the reference " Contractors": first search is performed by INN and Checkpoint(if these values ​​are filled), then only by INN and finally by Name... In all three cases, the group attribute (ThisGroup) and the group itself (Parent) are involved in the search. This is important for repeated (regular) transfers, so as not to create duplicates for counterparties with names changed AFTER loading.

When transferring counterparties, the requisite is filled Country of Registration meaning "Russia". This is necessary so that after loading the directory of counterparties into the program "1C Accounting 8" I didn't have to manually fill in the required details Country of Registration... If it is not filled in, then in the form of a directory item " Contractors"requisites will be available" Tax number" and " Reg. room"and the details" INN" and " Checkpoint"will be hidden.

In the rules for transferring "USN 7.7 - BP 3.0", a rule for unloading data for transferring the "Employees" directory has been added (in the standard rules, only the directory of individuals is transferred).

In the transfer rules "USN 7.7 - BP 3.0", the rule for transferring the information register "Current Tariff Rate" of Employees has been corrected.

Peculiarities of transferring payment orders for payment of taxes

For payment orders with an operation type Transfer of tax additional details must be filled in: KBK - code budget classification, originator status, etc. The structures of these props in Bukh 7.7 (USN 7.7) and in BP 3.0 do not match. In particular in BP 3.0 some of these details are included in a separate directory Types of taxes and payments to the budget, the link to which is contained in the payment order. The reference book contains a number of supplied elements that appear in the infobase, for example, when editing an accounting policy. When transferring data, these items will also appear when loading an accounting policy. When unloading and loading payment orders, a directory element Types of taxes and payments to the budget searched for by the KBK for substitution in the payment order details Tax... Therefore, it is recommended that after transferring the accounting policy, check whether all the necessary taxes have appeared in the reference book, if necessary, supplemented. When comparing (synchronizing) the BCC in payment orders in the source and the receiver, four BCC digits, categories 14-17, the code of the income subspecies are not taken into account: tax, penalties, penalties, etc. In the reference Types of taxes and payments to the budget these bits are filled with zeros. When adding new elements to the directory, digits 14-17 should also be filled with zeros.

Transfer of infobases big size.

First of all, when transferring large infobases, the data unloading process can take a very long time. This happens if there is a large number of balances for one section of accounting, for example, balances of goods. To reduce the time of unloading, you can apply the technique of splitting one document " Entering initial residuals" for a few. If you set the parameter value " The number of lines in the document for entering residuals"other than zero (see Fig. 6.3), then uploading data into one document will be limited to the specified value. This can significantly (several times) reduce the upload time.

Fig.6.3 Setting parameters when transferring data with document size limitation " Entering initial residuals»

Note: the value of this parameter limits the number of rows of the transactions table that are uploaded into one document " Entering initial residuals”, Rather than specifying the number of lines of the document itself. Therefore, the number of document lines will differ from the parameter value, this is not an error. When splitting a document " Entering initial residuals»For several documents, a postfix will be added to the comments of each document at the end of the line:" -1 "," -2 ", etc.

IMPORTANT! The described algorithm for splitting one document “ Entering initial residuals»Is used by a few only to reduce the time for uploading data, all documents are uploaded to one file, i.e. data transfer occurs in one step, comments (postfixes) are generated automatically, only one parameter is set. But this technique does not solve the problem of lack of memory, which will be discussed below.

When migrating large infobases, there may be a problem of shortage random access memory: When attempting to unload, the program will exit with or without an appropriate error message. Trying to replace your computer with a more powerful one is useless. In this case, you should unload the data in chunks, dividing them into portions. This requires migration rules that support the specified mode. Let's consider how to unload. First, data transfer should be performed using only one upload rule (see Figure 6.4). If the transfer is also impossible according to one rule, then we divide it into parts, indicating the initial and final portions. Each portion will contain information on a given number of first-level analytics values, for example, product balances, i.e. the specified number of values ​​of account balances "41". Knowing the total number of analytics on the account, it is easy to calculate the number of portions. How much data is transferred without problems at one time (in one piece of information) needs to be determined empirically, as a rule, when unloading account balances, transfer problems appear when the number of balances is several thousand or more. Although, to save time for uploading data, it is possible to recommend splitting into parts, even if all the balances for the accounting section can be unloaded at one time. The unloading time depends on the size of the data portion not proportionally, not linearly. Therefore, breaking, for example, ten thousand balances by goods into ten parts by a thousand, you can reduce the time of unloading at times. If we transfer the first portion, the number of the initial portion can be omitted, if the last portion, then the number of the final portion can be omitted.

IMPORTANT! When transferring data in parts, it is necessary to indicate in the parameters the postfix, which is involved in the formation of the document comment “ Entering initial residuals". When changing the numbers of the portion range, do not forget to change the postfix, otherwise, when loaded into the Receiving Configuration, documents with the same comments (postfix) will be overwritten. The name of the data file does not really matter. You can apply sequential transfer tactics: unload - load, unload - load, etc. In this case, the name of the data file does not need to be changed. You can choose a tactic: first unload everything, then download everything. In the latter case, the name of the data file will have to be changed each time it is uploaded. Another example. If the number of balances in the accounting section (for example, goods), let's say 10,000, is divided into parts by a thousand, then you get 10 portions. Each part must have a unique postfix: "-1", "-2", "-3", "-4". If we unload all the leftovers of goods, and then load everything, then the data files must also be unique, for example: "41_1", "41_2", "41_3", "41_4". The parameters "Batch number start" and "Batch number end" must take values: 0, 1000; 1001,2000; 2001, 3000; 3001, 4000.

Fig 6.4 Setting parameters when transferring data in parts

Data transfer in chunks is supported for the following upload rules:

Fixed assets

Materials (edit)

Deviations in the cost of goods and materials

VAT on purchased assets

Unfinished production

• Finished products and semi-finished products

  Selling expenses

  Goods shipped

  Cash

  Financial investments

  Settlements with suppliers and contractors

  Other settlements with counterparties

  Taxes and fees

  Payments to personnel

  Calculations with accountable persons

  Settlements with founders

  Settlements with other debtors and creditors

  Capital and reserves

  Future expenses

  Deferred tax assets and liabilities

  Financial results

  Off-balance sheet accounts

Do not try to follow ridiculous advice such as: "Move the reference books first, and then the leftovers." Firstly, there is no point in moving the reference book separately, at least in parts, at least in whole , if an error occurs when unloading leftovers, then this will not help... The error is most likely to actually occur when transferring residues (when unloading, it is important to understand), when the directory is transferred by links. It doesn't matter if the guide has already been migrated or not, when unloading leftovers, it will still be unloaded without restrictions. Secondly, transferring entire directories is usually garbage transfer, you should not do this.

After the end of the unloading you need to run the program "1C: Accounting 8". Download both initially and for repeated data transfers or additional transfers should be done using typical processing(see fig. 7).

Attention, important... Treatment Generic XML data exchange (in some releases 3.0.43.x) contains errors. Corrected processing can be used Generic XML data exchange, which is included in the delivery and is installed in the database directory Accounting version 4.5.

After loading into the program 1C: Accounting 8 the balance entry documents must be posted, and the rest of the documents must be re-posted. This is best done with processing Group reposting of documents, which is in the section Administration... If it is not visible in the specified section, configure the action bar by adding the required command (see Figure 7.1)

Figure 7.1 Action bar customization

Important... You cannot use processing from the typical configuration, since it works in the handler debug mode (ExchangeProcessing.FlagHandlerDebugMode = True) and does not allow the handler to be used "Search fields" to find loaded items for the reference " Contractors"(see above). More precisely, all handlers that are used during loading are in the processing built into the configuration HandlersDownloadsFrom Accounting77... Thus, it is not possible to carry out the migration according to the changed rules, at least during the download phase.

You can use a similar external processing Data TransferFrom Information Databases1CEnterprises77(it is included in the delivery). Below is described how to use it (once again - external processing).

After the end of the unloading you need to run the program "1C: Accounting 8". On the menu: File - Open and point to external processing Transfer of Data from Information Databases 1С of the Enterprise 77.

After that, a form will be displayed in which you must specify the option for loading data - Load data from file (Figure 7.2).

Then a dialog box will appear, in which you will need to specify the path to the uploaded file (see Fig. 7.3).

By clicking “Load data”, start the process of loading data (see Fig. 7.4), after which it will be necessary to generate a balance sheet and reconcile the turnovers in the database of the Source Configuration and the Receiving Configuration into which the loading was made.

If any errors occurred during the data transfer, a message window will open, from which, by double-clicking the mouse, you can proceed to eliminate the error. To receive a report on the errors encountered with a description and recommendations for elimination, you must click the hyperlink " Error information».

Loading during repeated data transfers or additional transfers of individual documents or directories can be performed using generic processing "Universal Data Exchange in XML", this will speed up the process.

Data Conversion Technique.

Conversion, if necessary, can be carried out in several stages, for example, first leftovers, and then documents. Re-transfer of information is possible.

The balances are transferred by means of documents " Entering initial residuals».

More information on the method of entering balances can be found in the article on the ITS website of 1C (for 1C: Enterprise Accounting revision 3.0)

Important! Before entering the initial balances, the parameters of the accounting policy must be set. The parameters of the accounting policy of the organization are read on the date following the date on which the balances are entered. For example, if the date of entry of balances is 12/31/2013, then the accounting policy parameters set as of 01/01/2014 are taken into account.This allows you to take into account the parameters of the current accounting policy (for example: if in 2013 the organization applied a simplified taxation system, and . switched to common system- then when entering balances as of December 31, 2013, the parameters of the accounting policy of 2014 will be taken into account). Make sure to accounting policy transferred correctly, correct if necessary.

Important! If you decide to start working in the recipient Configuration before you transferred the leftovers there, you must first transfer the directories before starting work in the recipient configuration. Otherwise, when transferring the remainders to a non-empty base, errors are possible.

I am answering the questions! Processing and transfer rules included in the delivery set are open, not protected in any way from copying. This does not mean that the buyer (licensee) has the right to distribute and replicate. The licensee does not have such a right. The licensee has the right to use. By exercising this right, the licensee can create archive copies, make changes, use an unlimited number of times on an unlimited number of computers. To improve or correct the conversion rules, as well as for a more detailed acquaintance with them, you need to load the rules into the program Data conversion... This program is distributed by 1C, and it defines the rules for its use.

Reasons to buy

Updated regularly. Updates are free for six months after purchase. It is included in the TOP-100 of Infostart publications.

Advantages

The text of the rules and processing are open, the data conversion technology is used, it is easy to edit.

Version comparison

01/29/2019 Rules updated to release 3.0.67.70

07/05/2018 Rules updated to release 3.0.63.22

09/25/2017 Rules updated to release 3.0.52.36

07/18/2017 Rules updated to release 3.0.51.16

10/12/2016 The error of transferring technical and technical equipment with old types of receipts has been fixed

09/08/2016 Rules updated to release 3.0.44.102

06/18/2016 Fixed the error of transferring manual operations that have a sub-account Subdivision

05/31/2016 The rules have been updated to release 3.0.43.236. In typical configurations (BP releases 3.0.43.174 - 235), in UniversalXML processing, the LoadParameters procedure does not work correctly. The rules have been changed to work around this bug. It is also possible to use UniversalXMLData Exchange (UniversalData Exchange) processing nested in the delivery package for loading into BP 3.0. It is written during installation into the ExtForms subdirectory of the inf directory. bases 7.7.

05/25/2016 Rules updated to release 3.0.43.215

05/11/2016 Limit on the length of the name of the contract changed from 50 to 100.

02/23/2016 Rules updated to release 3.0.43.29

12/21/2015 Processing and rules updated to release 3.0.42.33

11.11.2015 Added check for synchronization mode

05/18/2015 Processing and rules updated to release 3.0.40.24

05/14/2015 The transfer of payment documents for the payment of taxes has been improved

04/08/2015 Processing and rules updated to release 3.0.39.56. In release 3.0.39, the structure of the invoice for payment has changed: there is no more tabular section "Services", now there are goods and services in one tabular section "Products". Therefore the rules for 3.0.38 cannot be used to migrate to 3.0.39

04/02/2015 Processing and rules updated to release 3.0.38.53

12/23/2014 Processing and rules updated to release 3.0.37

Contents of delivery.

The scope of delivery includes: processing "ACC_ACC8", transfer rules "ACC_ACC8" and processing Data TransferFrom Information Databases1CEnterprises77... If your organization does not have a full-time programmer to carry out the work, we are ready to offer the services of our specialist (the programmer will connect to your computer via the Internet, via special program for remote work and will do the necessary work). If it is possible to provide a working base "1C: Accounting 7.7", we can transfer the data ourselves and transfer the file " 1C: Accounting 8"with the balance carried over. The cost of this service is not included in the total cost of the package.

© Boris Balyasnikov, January 2014, last changes January 2019

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

Take just a few steps and your data migration problems will be solved. Read on this manual to the end, and you will see a way how to do it. First, you must prepare workplace on your computer for the necessary manipulations. First, your HDD must be at least 100 GB in size. This is necessary because it is multi-level. And you will need to work with multiple 7.7 configurations.

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

Transfer of data from 1C 7.7 to 1C 8.3 accounting 3.0

So, before working with data transfer 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, with which your accountants work. Using Export77 processing, unload all the necessary documents into a text file and from this moment no longer return to the main working base. Your further manipulations will occur with other configurations.

Install the fresh Release 1C: Enterprise 7.7 into the new directory. (package includes standard blank (no data) and demo). We will be working with the standard version. Now start this database and use Import 77 to load the data from your main database from a text file.

When converting data, some documents may not be posted. 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 sub-accounts are, in your working base it is easy to fix it in about 3 hours by going into each unposted document and changing the accounts that you have in your configuration in the fields of the account.

Naturally, in advance, before the transfer, you bring the chart of accounts of the standard configuration in accordance with the chart of accounts of your main working base. The options are purely individual, depending on the specifics of the work of your organization. Having done this work, you get a standard configuration filled with data from your work base.

Now we need to do one more data transfer. To do this, perform the installation of the default zero configuration again in the new directory. And already there, transfer the data from the standard configuration with your data. As a result, you will have an ideal base of version 7, 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 working data.

Everything! Launching 1C: Enterprise 8.2. We select "Data transfer from version 7.7." and enjoy how the program itself transfers data from your processed 7.7., repost documents and displays a comparative table of the balance sheet of versions 7.7 and 8.3.

Of course, there will be no 100% result. But by 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 the accounts or the fields (for example, "Agreement" or "Main cash desk"). It depends on how different your base is. 7.7. from the standard. As a result of all these actions, your version 8.3 working configuration will be able to issue accounting data through the balance sheet in perfect form.

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

by the way! If you need improvement of 1C programs, you can contact us!

Video on the transition from 1s 7.7 to 8:

Exercise: You want to transfer required documents from one base to another 1C base. And not by hand, but in one fell swoop.

Solution:
Consider an example of transferring documents as follows: unloading information into a text file from any configuration "1C: Enterprise 7.7" for loading into exactly the same configuration.
This requires processing, which can be downloaded. Download, unpack and save the "import-export" folder somewhere on your computer next to the databases.
Then we go point by point.
1. Open database number 1, which is full of documents, reference books, etc. We open the document journal and see what documents we need to copy to another database. For example, we only need to transfer accounts for December 2012.

2. In the menu, select File - Open - open the "import-export" folder (downloaded earlier) - select the "Export771.ert" file.
In the "Upload data" dialog box, enter the parameters:

• data upload interval: 12/01/12 - 12/31/12
• unload documents: put a tick on the document "Invoice"

Click the "Upload" button

A window with the unloading process should appear at the bottom. Be sure to wait for the "Processing complete" message.

After successful unloading, close and exit the base.

3. Open base number 2, which is supposed to be empty, in monopoly ... Data loading into the database is performed only in exclusive mode!
In the File menu - Open - open the "import-export" folder (downloaded earlier) - select the "Import77.ert" file.

• upload file name: "import-export" folder - "transfer.txt" file
• put a tick "Display message"

Press the "Download" button.

Here, no matter how long you wait, there will be no message about the completion of the download. Just watch to make sure the last loaded document is the end date. In our case, it is 12/31/12. Or remember the number of the last document.

Click the "Close" button.

4. Now you can go to the "document journal" and see all uploaded documents (invoices for December 2012).
A small note: bases for processing testing were created by copying. Thus, all documents in the base No. 2 were deleted, and reference books with elements were available.
In any other case, it is not known how the processing will take place and in what form the documents will be unloaded and loaded.

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 has not reworked up and down the configuration, then this article was written for you and will help you with the transition to 1C 8.3 or 8.2.

How to prepare the 1C 8.3 (8.2) base for the subsequent transfer of data from 1C 7.7 step by step

Before starting work, it is necessary to prepare the 1C 8.3 (8.2) database for subsequent data loading.

Step 1

Update the 1C database to the actual 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 monthly closing operations. Additionally, you can check the accounting through Service - Checking data for the transition 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 download of data in case of unforeseen situations. Select the top menu of the program Administration - Upload data, register the name of the upload file and the location of its saving.

Thanks to these preparatory activities delete from our database extra objects, the 1C base will become smaller. The results will be recalculated, 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 infobase to 1C 8.3, see the following video tutorial:

Transfer of 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 infobases is not supported. In accordance with the requirement of the company 1C must be done. Therefore, if in the 1C 8.2 database you select Service - Transfer of data from information bases 1C Enterprise 7.7, then we get an error:

But what if you really need to transfer to the version of the 1C 8.2 program?

Step 1. Unloading data from 1C 7.7

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

Let's start this processing: If everything is done correctly, the inscription should appear - Uploading data for 1C Accounting 8, 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;
• Data unloading rules - objects for unloading, 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 choose 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 installing checkboxes:

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

Step 2. Downloading to 1C 8.2 Accounting 2.0 from 1C 7.7

We choose Service - Transfer of data from 1C Enterprise 8 infobases, in the window that appears, select Load from file:

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

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

Transfer of data from 1C 7.7 to 1C 8.3 Accounting 3.0

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

Step 1

After updating the 1C infobase, you need to update the data upload rules. This can be done as follows.

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

Step 2. Unloading 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 the upload 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, 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 - described above), the ExtForms folder. This is the one that was 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;
• Data unloading rules - objects for unloading, 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 installing checkboxes.

You can unload in parts, creating several files, or you can unload all data at once. How to proceed depends on the specific situation. In the example, we unload 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 the infobase - the 1C 8.3 program will itself find the installed databases and try to connect to this infobase by copying the data from there. Using the settings, you can specify what to load and click the Load data button:

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

Transferring data from a modified standard configuration 1C 7.7 to 1C 8.3 (8.2)

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

• Transfer of functionality. V new configuration it is necessary to repeat the functionality that is present in 1C 7.7. Additional documents, reference books and details. Make unloading -CF of this base.
• at the end of the year. Compare turnovers across accounts before convolutions and after- they must be equal.
• Transferring data from a minimized 1C 7.7 database to a standard clean database of a new edition. Check the turnover data for accounts in 1C 7.7 and 8.2 or 8.3. In case of mistakes, correct them.
• In a clean database, into which the data was loaded from 1C 7.7, it is necessary to load the CF configuration file, in which the functionality from 1C 7.7 was repeated.
• Additional details of directories 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 sub-accounts, accounting types, off-balance accounts, currencies and compare with the same report from the 1C 8.3 (8.2) base into which the data was transferred: