Data preparation
Match your source fields to ERPNext, find gaps and duplicates, and decide which records to move.
Move to ERPNext. Keep daily work moving.
Moving from QuickBooks, Tally, Zoho Books or spreadsheets? We review your exports, agree which records and history to move, and check the numbers before you switch. We also connect the tools you keep and support existing ERPNext systems.
WHAT’S INCLUDED
Match your source fields to ERPNext, find gaps and duplicates, and decide which records to move.
Import sample records and compare balances, counts, and transactions before moving the full set.
Investigate problems, fix agreed issues, test the affected tasks, and document the changes.
MIGRATION PATHS
Start with your software version, a sample export and the date you want to switch. We agree which records will move, test the import and reconcile the result with your finance team.
The old built-in QuickBooks Migrator is no longer available in current ERPNext releases. We plan an export-and-import migration using current ERPNext tools.
Frappe’s Tally Migrator is currently tested on ERPNext v16 and TallyPrime. It covers masters and opening balances; historical transactions, TDS/TCS and payroll need a separate plan. GST fields require India Compliance.
Zoho Books provides spreadsheet exports and backups. We check the actual files before confirming history, attachments or custom-field coverage; a backup is not an ERPNext-ready import.
The migration scope is conditional on the export review. We confirm what can be imported, what needs manual preparation and which history stays in the old system before quoting the work.
We review a representative file from each record type. Unsupported fields, custom workflows and detailed history are scoped separately after that review.
An opening-balance migration brings the records and unpaid amounts needed to continue trading from an agreed date. Moving closed invoices, settled payments and older journals is a separate scope: we first check whether the source detail can be recreated reliably. Keep the original records accessible for historical reporting.
Before switching, reconcile the trial balance, receivables, payables, bank, stock and other agreed control accounts. Check that opening invoices and ledger entries have not counted the same balance twice. Your finance owner approves the results and the final switch date.
We confirm the ERPNext and India Compliance app versions, then map GSTINs, registration types, HSN/SAC codes, units and tax accounts. Your accountant reviews tax balances and sample invoices before go-live. E-invoicing, e-waybills and GST API access are agreed and tested separately where required.
ONGOING INTEGRATIONS
Ongoing integrations are scoped separately from the migration. For each connection, we agree which system owns the data, the direction and frequency of updates, and who handles failures.
Agree the flow for orders, customers, items, stock and fulfilment. Test SKU and tax mapping, cancellations, refunds and repeated events before enabling the connection.
Shopify’s connector moved to a separate Frappe app. ERPNext’s old WooCommerce integration was deprecated in v15. We verify a connector’s compatibility and supported flows, or scope custom API work.
Map provider settlements or bank statement files to the right ERPNext accounts. Test fees, refunds, combined payouts and duplicates, then reconcile the statement against accounting entries.
Importing a statement does not itself post the accounting entry. A direct bank feed or payment connection depends on the provider, region, app and access available.
Define the handoff for shipment requests, tracking updates or records shared with another system. Review the provider’s API, access permissions and the fields each side needs.
Carrier and app support is checked for your setup. We test failed requests, safe retries and duplicate prevention, and agree monitoring and maintenance responsibilities.
HOW DELIVERY WORKS
STEP 01
Review sample exports for a migration, or reproduce the problem in your existing ERPNext setup.
STEP 02
Try imports or fixes in a test environment before changing your live system.
STEP 03
Move the data or apply the fix, check the results with your team, and document what changed.
Move to ERPNext. Keep daily work moving.
We assess your exports and migrate agreed records into ERPNext’s accounting module. The old built-in QuickBooks migrator has been removed from current ERPNext releases, so we plan the import around your source data and target version. Opening balances, unpaid invoices and required history are agreed before work starts.
Yes, a store can stay in place while ERPNext manages agreed operations. We first check the connector, supported versions and data it can exchange, then test orders, stock changes and failures. Ongoing synchronization is a separate piece of work from the initial data migration.
That depends on your exports, data quality, and the records ERPNext can accept. We check samples first and agree what moves and what stays available in your old system.
Yes. We review its version, customizations, documentation, and reported problems before quoting the work.
Support can cover troubleshooting, agreed fixes, and maintenance. Your proposal states the covered work, service hours, and response expectations; hosting is agreed separately.
RELATED SERVICES
Tell us about your current systems or website, what needs to improve and what you want to achieve.