First decide whether you are leaving QuickBooks or keeping it for a specific job. Moving opening records once and exchanging new invoices every day require different work, controls and support.
Choose migration or ongoing integration
If ERPNext will replace QuickBooks, agree a cutover date, reviewed exports, opening records and an accessible history archive. If both systems will remain, explain why and identify the records that must continue moving. ERPNext's former built-in QuickBooks Migrator is deprecated and unavailable in current releases. It is not a current continuous sync connector. A named external app needs a compatibility review; otherwise ongoing exchange is separately scoped custom API work.
- ERPNext's deprecated migrator notice
- Plan a one-time QuickBooks to ERPNext migration
- Discuss migration or continuing integration
QuickBooks Online and Desktop need different connections
QuickBooks Online uses Intuit's API and the account owner's authorization through OAuth for each connected company. Plan access-token renewal, withdrawn access and separate testing and production connections. Intuit's change notifications, called webhooks, cover supported record types; they do not perform the ERPNext mapping for you. QuickBooks Desktop uses different tools. Intuit's Web Connector is a Windows application that exchanges qbXML with a web service and depends on the Desktop machine or local network. Confirm the country, edition, release and company-file arrangement before promising support.
- Intuit's authorization and token management library
- QuickBooks Online authorization and supported notifications
- QuickBooks Desktop Web Connector architecture
Assign an owner to each financial record
Your finance owner should approve the ledger that controls reporting, account and tax mappings, invoice numbering and corrections to closed periods. Two systems editing the same transaction in both directions can create conflicting books. Start with the smallest useful agreed flow; the table describes decisions to make, not built-in connector features.
| Record | Ownership decision | Matching rule |
|---|---|---|
| Customers and suppliers | Choose the source of approved identity and currency details | Store the company and external record IDs; do not rely on names alone. |
| Products and accounts | Approve item, income, expense and tax mapping | Maintain an explicit mapping for each agreed record. |
| Invoices and bills | Choose which system creates and approves each document | Link both IDs and record the confirmed posting result. |
| Payments and credits | Assign allocation and correction responsibility | Match the relevant invoice, remaining amount and payment reference. |
| Stock | Choose the operational stock system | Define any agreed accounting exchange without a second uncontrolled stock ledger. |
Check currency and corrections with finance
Suppose a USD invoice is paid partly in USD while the company reports in INR. Both systems must agree the invoice balance, exchange-rate treatment and payment allocation. A net bank deposit after gateway fees is not automatically the invoice's full payment. Decide how credits, refunds, write-offs and rounding are represented. Test supported behavior for your QuickBooks edition and country. For Indian operations, separately confirm the applicable GST and invoice requirements instead of assuming that a foreign accounting setup supplies them.
Acceptance checks that protect the books
- Post an approved invoice and payment; match totals, tax, accounts and outstanding balance.
- Replay the same record after a timeout; confirm it is found rather than posted twice.
- Test a partial payment, credit or refund and any currencies you actually use.
- Revoke access or interrupt Desktop availability; confirm failures remain visible and recoverable.
- Attempt an unmatched item and a closed-period correction; confirm the agreed approval rule.
- Reconcile a day's source and destination records, with an owner for every difference.
Keep failures and future costs visible
A timeout may occur after QuickBooks accepted an invoice. Check the saved IDs and confirmed outcome before retrying. Define who repairs unmatched records, renews access and reviews missing transactions. Agree monitoring, update checks and the reconciliation schedule. Use a restricted Frappe integration account rather than shared administrator access. Fullsend assesses an external app or custom connection for the agreed flow; the quote separates integration, migration, third-party charges and maintenance from ERPNext module implementation. No automatic two-way coverage is assumed.
- Frappe API access and permissions
- See implementation prices and choose modules
- Connect Shopify orders with their own ownership rules
- Plan the WooCommerce order and stock connection
Related decisions
Official references: ERPNext QuickBooks Migrator deprecation and current migration tools · Intuit OAuth client and token management · Intuit QuickBooks Online webhook authorization and supported events · Intuit QuickBooks Desktop Web Connector · Frappe REST API authentication and document operations