Guide · Tally Import

Move from Tally
to SoloBooks.

Migrate ledgers, parties, and historical vouchers out of TallyPrime — your trial balances will match to the rupee.

Why migrate to SoloBooks?

Moving from desktop Tally to a cloud-native platform gives you real-time access to your books anywhere — and tools built specifically for Indian MSMEs: GST, Udhar Khata, multilingual receipts, party reminders, and a workflow your CA already understands.

Step-by-step import

1

Export Masters from Tally

Open TallyPrime → Export → Masters. Set format to XML (Data Interchange). Generates Master.xml containing all Ledgers, Stock Items, and Party details.

2

Export Vouchers (historical data)

Navigate to Export → Transactions or a specific Day Book / Register. Pick a date range and export as XML. Produces DayBook.xml.

3

Upload to SoloBooks

In your dashboard go to Settings → Data Management → Import from Tally. Upload Master.xml first, then DayBook.xml. Our parser handles structural mapping, balance validation, and GST checks automatically.

4

Verify and confirm

Review the summary of imported ledgers and vouchers. Click Confirm Import to write the records to your account. Trial balances should match Tally exactly.

Tip

Always upload Master.xml first. Vouchers reference ledgers and party names — if those don't exist yet, the import will reject mismatches.

Start your migration

Tally and TallyPrime are registered trademarks of Tally Solutions Pvt. Ltd. SoloBooks is an independent product, not affiliated with or endorsed by Tally Solutions.

FAQ

Tally import — common questions

Will my opening balances and history come across from Tally?

Yes. You export Masters (ledgers, parties, stock items) and Transactions (vouchers) from Tally as XML and upload both to SoloBooks. After import, your trial balance in SoloBooks should match Tally to the rupee.

In what order should I upload the Tally files?

Always upload Master.xml first, then DayBook.xml. Vouchers reference ledger and party names, so the masters must exist before the transactions are imported, otherwise SoloBooks will reject the mismatches.

Does importing from Tally create duplicate vouchers?

No. SoloBooks detects duplicates by matching voucher type, date, narration, and total amount, so re-running an import skips entries that already exist instead of duplicating them.

What happens if a voucher references a party that doesn't exist yet?

SoloBooks resolves parties by exact name first and then by phone number. If no match is found, it creates a new party record rather than failing the import.