Setup

Importing Data from Other Systems

Migrate customers, suppliers, products, opening balances and open items into IntBooks from CSV, Excel or supported tools, with preview and undo.

By IntBooks Editorial Team · Last updated: 29 September 2026

IntBooks’s Data Migration tool imports your records from CSV and Excel files, and from some accounting tools directly. This page covers what’s supported, how validation works, and how to undo an import.

What can I import?

  • Chart of accounts (see Chart of Accounts)
  • Opening balances
  • Customers and suppliers
  • Contacts
  • Products
  • Inventory balances
  • Tax codes
  • Open invoices and open bills
  • Leads

Historical journal entries aren’t imported. Bank transactions are imported separately, as bank statements (CSV, OFX/QFX or MT940) in Bank Recon.

File requirements

  • CSV or Excel (.xlsx or .xls)
  • Up to 10,000 rows and 10 MB per file
  • A header row naming each column
  • UTF-8 encoding for CSV files with Malay or Chinese characters, so names come through intact

There are no downloadable templates. IntBooks maps your own column headers instead (see below).

Step-by-step import

  1. Go to Data Migration and start a new migration.
  2. Choose the data type, and upload your file or connect a supported source.
  3. Review the column mapping. IntBooks suggests a match for each column; correct any that are wrong. You can save the mapping as a template for later.
  4. Review the preview. It shows what will be created or updated, and flags validation problems.
  5. Approve the preview to import.

How do I handle validation errors?

In the preview you can:

  1. Edit a record to fix the value.
  2. Set the conflict strategy for records that already exist: skip them, update them, or stop the import.
  3. Download the errors as a CSV, fix your source file, and upload it again.

Imports allow partial success. Valid rows are imported, and failed rows are listed with their errors.

What if I import the wrong data?

You can undo a migration within 24 hours:

  1. Open Data Migration and find the migration in the list.
  2. Choose Undo migration.
  3. IntBooks removes the records that migration created.

After 24 hours the undo option expires, because other transactions may reference those records. You’d then need to correct or delete records individually, which may not be possible once they’re in use.

Migrating from common tools

QuickBooks Online, Xero, Bukku, QNE

IntBooks has ready-made mappings for exports from these tools. For QuickBooks Online, Xero and Bukku, you can also connect your account and fetch the data directly.

SQL Account, AutoCount, MYOB and others

Export each list to CSV or Excel from your current software, then import it. There’s no ready-made mapping for these tools yet, so check the suggested column mapping carefully before you import.

From Excel

  1. Save your customer list as CSV or Excel with a header row.
  2. Import customers and check the mapping.
  3. Repeat for suppliers, products, opening balances, and open invoices and bills.

Tools without Malaysian tax fields

International tools may not hold Malaysian fields such as your customers’ TINs, registration numbers or SST registration numbers. Customer and supplier imports still work. Add the missing fields before you issue e-invoices. IntBooks’s post-migration readiness report counts what’s missing.

Best practices

  1. Import in order: chart of accounts → customers and suppliers → products → opening balances → open invoices and bills. This avoids reference errors.
  2. Test with a small sample first. Import 10 records, check the result, then do the full file.
  3. Keep your source files. If something goes wrong, you can undo and re-import.
  4. Import open items, not full history. Bring in balances and unpaid documents at your cut-over date. Keep your old system’s records for history.
  5. Clean up TINs before import. TINs are a prefix plus digits: C for companies, IG for individuals, and so on. Non-individual TINs end in 0; older records may have the retired SG/OG prefixes or be missing the final 0 (LHDN TIN guide). The import doesn’t check TIN format, and MyInvois rejects invalid TINs when you submit an e-invoice.

See also