Moving to TamilAccounting: Import Your Data Without Retyping It

Bring items, customers, suppliers, opening balances and outstanding invoices into TamilAccounting from Tally or any other system, with templates, validation and a guided migration wizard, so day one already agrees with your old books.

VVaradharaj V
Varadharaj V
Oct 06, 2026 · 4 min read
Moving to TamilAccounting: Import Your Data Without Retyping It

Switching accounting systems has one part everyone dreads: retyping years of customers, items and outstanding invoices from scratch. TamilAccounting does not make you do that. Everything a business needs to bring across — from a full migration out of Tally to a single spreadsheet of opening balances — lives in one place: Setup → Import.

Start with what you already have

If you are coming from Tally, Zoho, QuickBooks, Xero, Sage 50 or SMACC, start with Migrate from Software. Pick the software you are leaving and upload the file you exported from it. The wizard reads the file, shows how many rows already exist against how many are genuinely new, lets you check the column mapping, and only commits once you confirm it.

Build the master data first

Every other document in the system points back to a small set of master records, so they come across first:

  • Items — your product list: code, name, category, cost and opening quantity.
  • Customers and their Branches — who you sell to, and where.
  • Suppliers — who you buy from.
  • Employees Information — your staff register, ready for payroll and attendance.

Each has its own downloadable template, because each needs its own columns — a customer needs a credit limit, an item needs a cost. Get the structure right here, and everything built on top of it is right too.

Set opening balances so day one is accurate

Once the master data is in, the books need to open exactly where the old system left off. Customer Opening Balance and Supplier Opening Balance import each party's outstanding amount as of your switch date against one intermediate account, instead of a journal entry written by hand for every single one. Chart of Accounts brings your account codes and structure across as they are, so the categories your old reports used are the ones your new reports use too.

A worked example: moving off Tally

Picture a trading business with four hundred items and three hundred customers, switching on the first of the month. Week one: Items and Customers go in through Migrate from Software, the wizard flagging a handful of duplicate item codes to clean up first. Week two: Customer Opening Balance, Supplier Opening Balance and Chart of Accounts go in as of the switch date, so the first trial balance in TamilAccounting matches Tally's closing trial balance to the rupee. Week three: outstanding Sales and Purchase Invoices come in, and the last bank statement is imported and reconciled. By month two, every number agrees with the old books, and nobody typed a balance by hand.

Bring in outstanding transactions

Whatever was still open on switch day comes in next: Sales and Purchase Invoices still waiting for payment, Journal Entries for anything off the standard forms, Inventory Adjustments after a physical count, and Inventory Transfers — rows sharing the same date, source and destination group automatically into one transfer document. Bank Statements reads your bank's own export format from a template built for that bank, and the result lands directly in Imported Bank Inquiry, ready for reconciliation.

Manufacturing recipes and the CRM pipeline

Manufacturers bring in Bills of Materials and Sales Kits, so production and bundled selling are ready without rebuilding every recipe by hand. Businesses running a sales pipeline bring in Leads and Opportunities, so prospects the team was already chasing do not go cold just because the system changed underneath them. Allowances carries the payroll allowance structure across. A specialised trade app such as BurialPro adds its own import types on this same screen, for that trade's own records.

Every import ships a template and checks before it commits

Every import offers a downloadable template, so the columns filled in are exactly the columns expected. Nothing is committed blind, either — each import validates every row first, and a bad row is reported with its row number and the reason, not silently dropped.

Imported once, used everywhere

None of this data sits in a corner once it lands. An imported customer is immediately usable on a sales order. An imported opening balance is immediately in the financial statements. An imported bank statement is immediately in Imported Bank Inquiry, waiting to be reconciled. Import is simply how existing data enters every other module.

A job you do once

Data import is not something most businesses touch every week. It is a careful, one-time project: master data first, opening balances next, outstanding transactions last. Do it properly at the start, and every module opened afterwards — Sales, Purchases, Financial Statements, Payroll — already agrees with the business actually being run.

Filed under: Product Onboarding
Share this article
VVaradharaj V
Written by

Varadharaj V

Founder & CEO of TamilAccounting. A full-stack technologist from Karur, Tamil Nadu — building cloud-native, multi-country ERP for the next decade. 9+ years across GST, VAT, ZATCA, FTA and white-label reseller systems.

Try It Yourself

Run your entire business on one ERP.

Sales, purchases, inventory, manufacturing, HR & payroll, banking, tax filings — already linked. 1-month free trial, no credit card.

Start Free Trial
Global Coverage

Multi-Country ERP — One Platform

Supports GST (India), VAT (UAE, South Africa, Egypt, Iraq, Botswana), and local compliance across all regions.

🇮🇳 India (GST)
🇦🇪 UAE (VAT)
🇸🇦 Saudi Arabia
🇶🇦 Qatar
🇧🇭 Bahrain
🇴🇲 Oman
🇰🇼 Kuwait
🇪🇬 Egypt
🇮🇶 Iraq
🇿🇦 South Africa
🇧🇼 Botswana
🇲🇾 Malaysia
🇸🇬 Singapore
🇦🇺 Australia
🇬🇧 United Kingdom
🇺🇸 USA
🌏 & More Regions