Data migration
The data migration tool brings a company's data into Thoshika from the software it uses today. Open Admin, Data migration. Company administrators can import anything; an app's administrator can import that app's records.
Sources
| From | What comes across |
|---|---|
| Tally Prime and ERP 9 (XML export) | Groups, ledgers, parties with GSTIN, stock items, godowns, sales and purchase vouchers, receipts, payments, journals, credit and debit notes, and openings |
| Zoho Books (export zip or CSV) | Contacts, items, chart of accounts, invoices, bills, payments and openings |
| QuickBooks (IIF, or QuickBooks Online CSV) | Lists, transactions and opening balances |
| Keka, greytHR, Darwinbox, Zoho People | Employees with job, organisation and manager; PAN, Aadhaar, UAN, ESI and bank details; salaries; leave balances; current-year payroll for TDS; attendance |
| Zoho CRM, HubSpot, Salesforce | Leads, accounts, contacts and deals with owners, sources and stages |
| Any spreadsheet (CSV or Excel) | Any supported record, including support tickets, procurement vendors and items |
Importers read each product's published export format and are tested with sample files. Thoshika is not affiliated with these vendors; product names belong to their owners.
Files can be CSV, Excel, a zip of those, Tally XML or IIF, up to 60 MB or 200,000 rows.
Steps
- Upload. Choose the source and upload the file. Thoshika recognises the format and suggests a mapping.
- Map. For each dataset, check which Thoshika field each column fills. Saved mappings are reused next time.
- Validate. Thoshika checks required fields, numbers, dates and emails, and validates IDs such as PAN, Aadhaar and GSTIN. Bad IDs are reported but do not stop the import.
- Dry run. The whole import runs with all of the app's rules and is then rolled back. You get the rows that would be rejected, with the reason for each, as an Excel download.
- Import. Records are imported in batches. Rows that fail are reported; good rows are saved.
- Check the report. You see counts of new, updated, skipped and rejected records. For accounting imports, the report shows the trial balance and any amount left in opening balance equity, which should be zero when ledger, party and stock openings agree.
Running again and rolling back
- Re-running the same source updates masters (parties, items, accounts, employees, leads) and skips documents that are already posted, so nothing is duplicated.
- Rollback undoes what an import created: payments and invoices are voided, journals reversed, parties and items deactivated, employees ended with the reason "Imported in error". Records the import only updated stay as they are.
Tips
- Run a dry run on a full export before the real import, and fix rejected rows in the source file.
- Import people before salaries, leave balances and attendance.
- For accounting, import the chart of accounts and parties before documents, and set your opening balance date first.
Not available yet
Pulling data live from Tally or other systems, attachments, foreign-currency documents and payslip history from earlier financial years are on the roadmap. For TDS, payroll figures for the current financial year are imported.