AutoCount transaction migration

AutoCount Transaction Migration — Historical Transaction Import for Malaysian SMEs

AutoCount transaction migration is a data import service for Malaysian SMEs that need to bring historical transaction data into AutoCount — sales invoices, purchase invoices, AR receipts, AP payments, GL journal entries, credit notes, debit notes, stock movements, and other transactional records from your previous accounting system or Excel-based records. Unlike master data migration (which imports customer, supplier, and item records), transaction migration imports the actual business transactions — giving your AutoCount system a complete financial history rather than just opening balances. RM500 per year of transaction data per account book.

Why AutoCount Transaction Migration?

When businesses switch accounting systems, the standard approach is to import master data and opening balances into the new system — then start fresh with transactions from the go-live date. This means all historical transactions stay locked in the old system. Need to look up a customer's invoice from 6 months ago? Open the old system. Need to check a supplier payment from last year? Dig through the old database. Need to pull 2 years of transaction history for an audit? Run reports in two separate systems and consolidate manually.
Transaction migration eliminates this. Your historical invoices, payments, purchases, and journal entries are imported into AutoCount — giving you one system with complete transaction history. No more switching between old and new systems. No more maintaining a legacy database just for historical lookups. Everything is in AutoCount.

What We Migrate

Sales Transactions

Import historical sales invoices, cash sales, credit notes, and debit notes into AutoCount. Each transaction is created with the original document date, document number, debtor, line items, quantities, prices, tax amounts, and totals. Your AR history is complete — customer transaction history, aging analysis, and sales reporting include all historical data, not just post-migration transactions.

Purchase Transactions

Import historical purchase invoices, goods received notes, purchase returns, and purchase debit notes. Each transaction records the original date, supplier, items, quantities, costs, and tax amounts. Your AP history is complete — supplier transaction records, creditor aging, and purchase analysis cover the full trading period.

AR Receipts & AP Payments

Import historical customer receipts and supplier payments — including payment dates, amounts, payment methods, cheque numbers, and bank references. Receipts are matched to the corresponding invoices for accurate aging and outstanding balance calculations. Payments are linked to the correct purchase invoices for supplier account reconciliation.

GL Journal Entries

Import historical general ledger journal entries — adjustments, provisions, accruals, depreciation entries, intercompany postings, and any other GL transactions. Each entry maintains the original date, account codes, descriptions, and debit/credit amounts. Your GL history and trial balance are continuous from the old system through to AutoCount.

Stock Movements

Import historical stock transactions — goods received, stock issues, stock adjustments, stock transfers, and other inventory movements. Each transaction records the item, quantity, location, date, and reference. Your stock card history shows complete item movement from the old system forward — not just from the AutoCount go-live date.

Other Transactions

Depending on your previous system and data availability, we can also migrate quotations, sales orders, purchase orders, delivery orders, and other document types. The scope is determined by what data you have available for export and what transaction history your business needs in AutoCount.

Data Sources We Accept

✅ Excel (.xlsx, .xls) — transaction listings exported from any system

✅ CSV (.csv) — standard export format from most accounting software

✅ SQL Accounting — transaction data exports

✅ UBS Accounting — historical transaction records

✅ MYOB — transaction exports

✅ Other accounting systems — any system that exports to Excel or CSV

✅ Database backups — direct data extraction from MSSQL or other database formats where accessible
If your historical transactions exist in any extractable format, we can migrate them.

How Transaction Migration Works

1. Export Your Transaction History

Export transaction data from your previous system — by year, by transaction type, or as a complete data dump. We provide guidance on what fields are needed for each transaction type. The more complete the exported data, the more accurate the migration.

2. We Clean, Validate & Map

We review the exported transactions for data integrity — missing fields, duplicate entries, unbalanced journal entries, orphaned payments without matching invoices. Transaction dates, document numbers, account codes, and amounts are validated. Your data fields are mapped to AutoCount's transaction structure — ensuring every field lands in the correct place.

3. We Import Year by Year

Transactions are imported in chronological order — oldest year first — to maintain correct running balances, aging calculations, and sequential document numbering. Each year's transactions are verified before proceeding to the next year. This ensures AR/AP balances build correctly and stock balances accumulate accurately across the migration period.

4. We Verify & Reconcile

After import, we verify that key totals match between the old system and AutoCount — total AR outstanding, total AP outstanding, total revenue per period, total expenses per period, closing stock value, and trial balance. Any discrepancies are investigated and resolved before handover. Your AutoCount books match your old system to the ringgit.

Who Needs AutoCount Transaction Migration?

Businesses Switching Accounting Systems

Malaysian SMEs migrating from SQL Accounting, UBS, MYOB, or any other system to AutoCount who want complete transaction history — not just master data and opening balances. One system for everything — historical and current.

Businesses Undergoing Audit

Companies facing audit that need historical transaction data accessible in one system. Auditors expect to see full transaction trails — sales, purchases, payments, and journal entries. Having everything in AutoCount eliminates the need to maintain and present data from two separate systems during audit.

Businesses Required to Retain Multi-Year Records

Malaysian businesses required by LHDN to retain 7 years of accounting records. Transaction migration ensures all 7 years are accessible in AutoCount — searchable, reportable, and audit-ready. No reliance on a decommissioned old system that may become inaccessible.

Businesses Decommissioning Legacy Systems

Companies that want to shut down their old accounting software permanently — no more license renewals, no more server maintenance, no more staff training on two systems. Import the transaction history into AutoCount, verify the data, and decommission the legacy system completely.

Accounting Firms Migrating Clients

Firms that move clients from legacy systems to AutoCount and need complete transaction history for each client. Each client's historical data is migrated into their AutoCount account book — the firm manages everything in one platform going forward.

Transaction Migration vs Master Data Migration

Master Data Migration (RM500 per account book) imports the foundational records — debtors, creditors, items, chart of accounts, and opening balances. Your AutoCount starts with correct balances but no transaction history. Historical lookups require the old system.
Transaction Migration (RM500 per year per account book) imports the actual transactions — invoices, payments, journal entries, stock movements. Your AutoCount contains complete transaction history. The old system can be decommissioned.
Most businesses need both — master data migration first (to set up the foundation), then transaction migration (to bring in the history). A business migrating 3 years of history for 1 company: master data migration (RM500) + 3 years of transactions (3 × RM500 = RM1,500) = RM2,000 total.

Pricing

RM500 per year of transaction data per account book.
Migrating 1 year of transactions for 1 company = RM500.

Migrating 3 years of transactions for 1 company = RM1,500.

Migrating 5 years of transactions for 1 company = RM2,500.

Migrating 3 years of transactions for 2 companies = RM3,000.
Master data migration is a separate service at RM500 per account book — typically required before transaction migration.

What's Included

✅ Sales Transaction Import (Invoices, Cash Sales, CN, DN)

✅ Purchase Transaction Import (PI, GRN, Purchase Returns)

✅ AR Receipt & AP Payment Import

✅ GL Journal Entry Import

✅ Stock Movement Import (GR, Stock Issue, Adjustment, Transfer)

✅ Data Cleaning & Validation

✅ Field Mapping (Source Data → AutoCount Transaction Structure)

✅ Chronological Year-by-Year Import

✅ Post-Import Verification & Reconciliation

✅ Accepts Excel, CSV, SQL Accounting, UBS, MYOB, and Other Formats

✅ RM500 Per Year Per Account Book

✅ Compatible with AutoCount Accounting 2.2