How to Transfer Data When Switching Accounting Software? Training on Moving Accounts and Products with Excel: A Step-by-Step Guide in 8 Lessons
How do you transfer accounts and products when switching accounting software? Excel template, data cleanup, test import and balance reconciliation: an 8-lesson step-by-step training.
Contents 14 sections
- What will you be able to do by the end of this training?
- Lesson 1: How do you set the transfer date and scope?
- Lesson 2: How do you take a data inventory?
- Lesson 3: How do you clean data before the transfer?
- Lesson 4: How do you prepare the Excel template?
- Lesson 5: How do you run a test import and read the result?
- Lesson 6: How do you do the bulk import?
- Lesson 7: How do you verify the transfer with balance reconciliation?
- Lesson 8: How do you run in parallel and shut down the old software?
- What are the most common mistakes in data transfer?
- How is your data protected in NetKasam, and how can you take it back if needed?
- Mini quiz: Test what you have learned
- Conclusion: a transfer should be a proven move, not an upload
- Frequently Asked Questions About Accounting Software Data Transfer
Deciding to switch to new bookkeeping software is the easy part. The hard part is bringing the customer list, suppliers, products and balances built up over years into the new system without losing anything and without carrying over faulty records. That is why most businesses put off the switch; some, a week later, hastily upload Excel files and then spend months hunting for balance differences. The answer to how do you transfer data when switching accounting software is not magic but a sequence of tasks: first you decide what will be moved, clean the data, try it with a small test, then import it in bulk and compare the figures one-to-one with the old system.
This article is not an ordinary narrative but an 8-lesson hands-on training. In each lesson you will find what to do, why you do it and how to tell you did it right. We will proceed with examples, test what you have learned with a 5-question mini quiz at the end and finish the job with a checklist. Account and product transfer with an Excel template is shown in NetKasam; most of the method, however, will serve you whichever software you switch to.
What will you be able to do by the end of this training?
In short: You will inventory the account and product data in your old software, clean it, put it into the Excel template, test it, import it in bulk and prove the transfer is correct by comparing balances and record counts. For a small business, about 5 business days at 1–2 hours a day is enough.
- 01InventoryDecide what will be moved and what will be archived.
- 02CleanupFix duplicate, inactive and incomplete records before the transfer.
- 03TemplatePrepare the data to fit the Excel template's format.
- 04TestTry it with 100 records, see the error types and fix them.
- 05Bulk importBring the clean data in at once.
- 06ReconciliationMatch the record count and balance total with the old system.
The training covers these 8 lessons: (1) setting the transfer date and scope, (2) taking a data inventory, (3) cleaning the data, (4) preparing the Excel template, (5) running a test import, (6) bulk import, (7) balance reconciliation, (8) running in parallel and shutting down the old software. Each lesson uses the output of the previous one; it is recommended that you keep the order.
Lesson 1: How do you set the transfer date and scope?
In short: Time the switch to the beginning of a month or year, and write down in advance which data will move to the new system and which will be archived in the old software. You do not have to move the entire history; starting with an opening balance is sufficient for most businesses.
The switch date determines how transactions are split between the two systems. If you choose the beginning of a month or year, you avoid a complicated split such as "old software until the 14th, new software from the 15th"; balances tie to the period with a clean line. Because VAT and other tax return periods are also monthly, a switch at the start of a month makes coordination with your certified public accountant (mali müşavir) easier.
The scope decision is just as important. Moving all historical transactions (years of invoices, collections, stock movements) to the new system is both difficult and often unnecessary. The common and safe method is this: bring customer and product cards, open balances on the switch date and stock quantities into the new system; archive historical transactions from the old software as reports and files. Legal retention periods are set by law; you need to be able to access the old software's data throughout that period. Ask your certified public accountant about the period and the archive format.
| Data type | Is it moved to the new system? | How? |
|---|---|---|
| Account cards (customers and suppliers) | Yes | Bulk import with an Excel template |
| Product cards (name, barcode, price, VAT) | Yes | Bulk import with an Excel template |
| Open account balances | Yes | The balance on the switch date, as an opening balance |
| Stock quantities | Yes | A count on the switch day or the quantity in the old software |
| Cash and bank balances | Yes | The balance on the switch date, as an opening entry |
| Historical invoices and transactions | Usually not | Archived from the old software as PDF and Excel |
| Old reports | No | Archived as of the switch date |
In this table, "bulk import with an Excel template" is the route NetKasam supports only for accounts and products; for how other data types are entered, refer to the user guide or the support team. In the rest of the training we will apply only account and product transfer, because the risk of error is highest in these two data types.
Lesson 2: How do you take a data inventory?
In short: Export the account and product lists from the old software as Excel, and gather the record count, field names and fill rate of each field on one sheet. The inventory shows which data needs cleaning before the transfer.
Most accounting software lets you export customer, supplier and product lists as Excel or CSV. Copy these files into a "raw data" folder; never do the actual work on these files, only on their copies. That way you can go back to the original if something goes wrong.
Then count three things: total number of records, field names (such as company name, tax number, phone, email, address, balance) and the percentage of records filled in for each field. For example, if 1,180 of your 1,250 account records have a tax number and 1,050 have a phone number, the inventory shows you the first gap: 70 records have no tax number.
Lesson 3: How do you clean data before the transfer?
In short: Merge duplicate records, separate inactive records that have had no transactions for a long time, and complete fields such as missing tax numbers and phone numbers. Cleaning before the transfer lets you fix an error in a few seconds per record; finding it after the transfer takes many times longer.
Three kinds of records are cleaned:
- Duplicate records: Cards opened for the same customer under two different spellings, such as "ABC Ltd." and "ABC Limited Company". The balance may be split between them; add up the balances before merging.
- Inactive records: Customers and products with no transactions in the last three years and a zero balance. Archiving these in the old software instead of moving them to the new system keeps the list lean.
- Missing and incorrect fields: Blank tax numbers, phone numbers, email addresses and addresses; badly formatted numbers.
Let's take an example business's account list: there are 1,250 records. After review, 85 duplicate records will be merged and 140 records will be set aside for archiving because they have had no transactions for three years and have a zero balance:
- Account records in the old software1,250 records
- Duplicate records (merged)−85 records
- Inactive records (set aside for archiving)−140 records
- Accounts to transfer to the new system1,025 records
Prepared with example values. An inactive record with a non-zero balance is not archived; its balance is settled first.
During cleanup, also remember what you use account cards for; if you want to review what a current account is and what it includes, see our article what is a current account.
Lesson 4: How do you prepare the Excel template?
In short: Download the new software's Excel template and fill it in without changing its headers; write each field in the format the template expects. The most common sources of errors are long numbers such as barcodes and phone numbers, tax numbers, VAT rates and currency format.
In NetKasam, core data such as accounts and products are imported in bulk with Excel templates. How to get the template and what the fields mean are explained in the user guide and training videos; when you get stuck, you can also ask the expert support team for help. Do not change the template headers, do not disturb the column order and do not add fields that are not in the template on your own.
Excel silently corrupts some values. The table below shows the five problems behind most transfer errors and the correct way to write them:
| Area | Common error | Correct format |
|---|---|---|
| Barcode | The value 8690000000017 appears as 8.69E+12 or the last digits are zeroed | Change the column to "Text" format and type it; do not enter barcodes as numbers |
| Tax number | The leading zero is deleted and digits go missing | Text format; 10 digits for companies, 11 for sole proprietorships |
| Phone | The leading 0 or +90 is lost; spaces and dashes get mixed up | Choose a single format (e.g. 5xx xxx xx xx) and apply it to all |
| VAT rate | 20% is sometimes written as 0.2, sometimes as 20 | The single format the template expects; the same everywhere |
| Price and balance | Comma and period get mixed up as the decimal separator; the thousands separator corrupts the figure | Choose one decimal separator; do not use a thousands separator |
Barcodes are especially important in e-commerce: because marketplaces match products by barcode, a corrupted barcode causes the product to be matched incorrectly or not uploaded at all. For how to create barcodes and their standards, see the barcode creation guide for e-commerce businesses.
Lesson 5: How do you run a test import and read the result?
In short: Before uploading all the data, run an import with a 100-record sample. Count the error types, find their source and fix the whole template. The test keeps you from uploading thousands of records with the same error.
When choosing the sample, do not just take the first 100 records; choose a mix of different kinds of records: individuals and companies, incomplete and complete fields, long and short company names, foreign currency. That way problems show up in the small sample.
Below is the result of an example test import: 82 of 100 records were uploaded without problems on the first try; 18 records gave errors for these reasons:
- Transferred without problems82 records82%
- Missing or incorrect tax number9 records9%
- Incorrect phone format5 records5%
- Duplicate company name4 records4%
This table tells you two things. First, all the errors are of a predictable kind: tax number, phone and duplicates. Second, you can fix these three error types in bulk across the whole template: filter the tax number column by digit count, convert phone numbers to a single format, and sort company names to find duplicates. Repeat the small sample until the test result reaches 100%; only then move on to the bulk import.
Lesson 6: How do you do the bulk import?
In short: Once the test passes without errors, bring in the whole template at once. Before the transfer, take a final export from the old software; do not enter new records during the transfer.
Follow three rules during the bulk import. First, keep the order: account cards first, then product cards, then balances and stock quantities, because balances depend on accounts and stock depends on products. Second, do not make new transactions in the old software during the transfer; otherwise the transferred file and the current data drift apart. Third, check the record count right after the transfer; if the number is not the same as in the template, do not move on to the next lesson.
In NetKasam you can create as many customers as you like; there is no limit on the number of accounts. Product variants are unlimited as well, so you can transfer sub-options like size and color as variants rather than separate products. The training videos on quick product creation and bulk product updates save time on price and stock corrections after the transfer; you can access them on the training videos page.
Lesson 7: How do you verify the transfer with balance reconciliation?
In short: After the transfer, compare the old software and the new system on three measures: record count, total account balance and stock value. The difference should be zero in all three; a non-zero difference is the trace of an error.
- Records to transfer = Total records − Duplicate records − Inactive records set aside for archiving
- Test success rate = Records transferred without errors ÷ Number of test records
- Record count difference = Records to transfer − Records in the new system (target 0)
- Balance difference = Total balance in the old software − Total balance in the new system (target 0)
- Stock value = Σ (product quantity × unit cost); should be the same in the old and new systems
Receivable and payable balances are added up separately; looking at the net balance can hide differences with opposite signs.
The example business's post-transfer comparison looks like this:
| Control | Old software | New system | Difference |
|---|---|---|---|
| Number of account records | 1.025 | 1.025 | 0 |
| Total receivable balance | 2.480.000 ₺ | 2.480.000 ₺ | 0 ₺ |
| Total payable balance | 1.315.000 ₺ | 1.315.000 ₺ | 0 ₺ |
| Number of products | 3.150 | 3.150 | 0 |
| Total stock quantity | 41.800 | 41.800 | 0 |
| Stock value (at cost) | 1.936.400 ₺ | 1.936.400 ₺ | 0 ₺ |
When all differences come out at zero, the transfer is verified. If a difference appears, the cause is usually one of a few things:
| Where is the difference? | Possible cause | Solution |
|---|---|---|
| Missing accounts | Duplicate records were not counted when merged, or badly formatted rows were skipped | Review the import error file and add the missing row to the template |
| Balance difference | The balances of two duplicate cards were not combined; currency or sign got mixed up | Add up the two cards' balances by hand and open them on a single card |
| Stock quantity difference | Products with negative stock, or a decimal separator error | Correct negative stock with a count before the transfer |
| Stock value difference | The unit cost field is empty or in a different currency | Check the cost column in the template again |
After internal verification, you can also do external verification: reconciliation with customers and suppliers who have large balances. In NetKasam you can send reconciliation letters to your customers with one click; this proves that the transferred balance also matches the other party's records. For details, see our article what is account reconciliation and how is it done. If you have doubts about stock quantities, doing a count on the switch day is the safest route; for the method, take a look at our guide how to do a stock count.
- 1,025account records to transfer after cleanup
- 82%first-try success of the 100-record test
- 3 typesof error seen in the test: tax number, phone, duplicates
- ₺0$0target balance difference; if not zero, the old software is not shut down
Lesson 8: How do you run in parallel and shut down the old software?
In short: After reconciliation shows zero difference, keep both systems open for a while, enter new transactions only in the new system and compare weekly. Shut down the old software after you have taken the report and document archive and a month-end close has gone smoothly.
- First week: Enter all new transactions in the new system; open the old software only to look things up. At the end of the week, compare the new system's account balances with the balance you calculate from the old software's switch balance plus transaction totals.
- End of the first month: Do the month-end close in the new system, send the new system's reports to your certified public accountant (mali müşavir) and confirm that the tax return data comes out consistent.
- Archive: Take all reports, invoices and transaction listings as of the switch date from the old software as PDF and Excel; store them in a safe place along with a backup.
- Shutdown: After verifying the archive, end the old software's subscription; do not shut it down without taking a final copy of your data.
- Invoice sequence: Remember that invoice numbers must be sequential; note your last invoice number on the switch day and check it before the first invoice in the new system.
After the transfer, you can make a few settings to start using the new system's strengths: you can define a risk limit for your customers' open balances and get reminders for payments coming due and overdue. If these were not available in the old software, they become the first gains of the switch. For all current account features, see the customer account tracking page; for the inventory side, see inventory management.
What are the most common mistakes in data transfer?
- Transferring without cleaning. Starting with duplicate and inactive records opens the new system with a dirty list from day one.
- Bulk uploading without a test. The same error repeats across a thousand records; a test shows the error types in 100 records.
- Writing barcodes and tax numbers as numbers. Excel deletes leading zeros and turns long numbers into scientific notation.
- Working on the raw file. When an error occurs, you have no point to go back to.
- Skipping reconciliation. A balance difference surfaces months later, at the first reconciliation or tax return period.
- Shutting down the old software immediately. A system shut down without an archive and backup is an irreversible loss of data.
- Setting the switch date in mid-month. Transactions split across two systems make balance comparison harder.
How is your data protected in NetKasam, and how can you take it back if needed?
The first question that comes to mind when moving data to a new system is security. NetKasam backs up your data in multiple locations and multiple times; it does this for you. If you also want to keep a backup on your own computer, you can export your data to Excel; and if you want to leave NetKasam, you can take all your data to your computer in Excel format. In other words, the switch is not a one-way door. For details, see the questions should I make backups and if I want to leave NetKasam, can I take my data.
You can also get step-by-step support for the transfer: as stated in the answer to the question can I transfer my data in bulk from my old software to NetKasam, the user guide and training videos explain how to do it, and the expert support team helps as well. The bookkeeping and e-Invoice (e-Fatura) system is free in every plan; plan details are on the pricing page.
Mini quiz: Test what you have learned
In short: Answer the 5 questions below, then compare with the answer key. 4 or 5 correct shows you have completed the training.
- Is the best date for the switch the beginning of the month or the middle?
- How many records are recommended for a test import, and why shouldn't you pick only the first 100 records?
- What format should the barcode column be in Excel?
- On which three measures should the difference be zero after the transfer?
- When is the old software shut down?
Answer key:
- The beginning of the month (or year); transactions are not split between two systems, and it aligns with the tax return period.
- 100 records; a mix of different kinds of records (individuals and companies, incomplete fields, foreign currency) should be chosen so that problems show up in the small sample.
- Text format; if entered as a number, the leading zero is deleted or a long number gets corrupted, like 8.69E+12.
- Record count, total account balance (receivable and payable separately) and stock value.
- After reconciliation shows zero difference, a month-end close has gone smoothly in the new system, and the archive has been taken and verified.
Frequently Asked Questions About Accounting Software Data Transfer
How do you transfer data when switching accounting software?
First you decide what will be moved, clean the data, prepare it to fit the Excel template, try it with a 100-record test and import it in bulk. Then the transfer is verified by comparing the record count, total balance and stock value with the old software.
Can I transfer my customers and products from my old software to NetKasam?
Yes. You can import core data such as accounts and products using Excel templates. The user guide and training videos explain the steps, and if you wish you can get help from the expert support team.
Do I need to move all historical transactions to the new software?
No. For most businesses, it is enough to move account and product cards, the open balances on the switch date and stock quantities. Historical transactions are archived as reports and files from the old software; consult your certified public accountant (mali müşavir) about legal retention periods.
When is the best date for the transfer?
The beginning of a month or a year. On that date, transactions are not split between two systems, and balance comparison and tax return periods are easier.
Why do barcodes and tax numbers get corrupted in Excel?
Excel treats long numbers as numbers; it deletes leading zeros and turns very long values into scientific notation such as 8.69E+12. These fields should be entered in "Text" format.
How do I know the transfer is correct?
You compare the record count, total receivable and payable balances and stock value with the old software. The difference should be zero in all three; if not, the old software is not shut down until the cause is found.
Can I keep using the old software during the transfer?
It is recommended not to enter new transactions into the old software during the transfer. Otherwise the transferred file and the current data drift apart and a balance difference arises.
If I want to leave NetKasam, can I take my data?
Yes. You can take all your data by exporting it to your computer in Excel format. NetKasam also backs up your data in multiple locations and multiple times.
Conclusion: a transfer should be a proven move, not an upload
What makes a data transfer reliable is not uploading quickly but proving each stage with numbers: the record count in the inventory, how many records were set aside in cleanup, the success rate in the test and zero difference at the end. When you apply the eight lessons of this training in order, the switch stops being a feared risk and becomes a measurable project. As a first step, export your account and product lists from your old software as Excel today, write down the record counts and copy them to the raw folder; this two-minute step is the foundation for the rest of the switch.
Bookkeeping Is Now Completely Free
Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.