QuickBooks Online (QBO) is a different shape from the field-service platforms above. It’s accounting-first, not job-first. Conduit pulls supported records into Conduit’s job-management model: customers, contacts, projects, jobs, bids, invoices, pricebook items, and schedules. Authentication uses OAuth via Intuit’s official handoff.
This guide walks the migration: connecting via OAuth, what transfers and what doesn’t (especially since QBO is accounting-shaped), and what to verify after.
01Connect to QuickBooks Online via OAuth
The OAuth handoff goes through Intuit’s standard flow. Conduit never sees your QBO password.
- Open Conduit’s migration wizard at Settings → Import Data → Import from Another Tool.
- Click the QuickBooks Online tile.
- Click Connect Account. A new window opens to Intuit.
- Sign in with your Intuit ID.
- Intuit asks: “Do you want to share data with Conduit for Contractors?” Click Connect.
- The popup closes. Conduit’s wizard advances to Pull Data.
If you have multiple QBO companies on the same Intuit ID, Intuit asks which company to connect. Pick the one for this Conduit account.
02What transfers
Conduit can import the supported record types QuickBooks exposes through the migration flow:
- Customers and contacts. Names, emails, phones, billing addresses, and customer type where it can be mapped.
- Projects and jobs. QBO sub-customers or job-shaped records can become Conduit projects or jobs when the source data exposes the relationship.
- Bids and invoices. Customer-facing sales records with line items, totals, payment status, and dates.
- Pricebook items. QBO’s item list becomes your Conduit pricebook. Each item maps to name, description, unit (best-effort), price, and cost when present in QBO.
- Schedules. Recurring or schedule-shaped source records can become Conduit recurring schedules when enough date and customer data is available.
Imported customer records store the source record ID in source_external_id so re-importing later can skip duplicates by source ID.
03What doesn’t transfer
QBO has a lot of data that doesn’t fit Conduit’s job-centric model:
- Journal entries, ledger transactions. Accounting plumbing doesn’t transfer; Conduit isn’t a replacement for accounting software, it’s a job-management layer that integrates with accounting.
- Bank feeds, reconciliations. Stay in QBO.
- Vendors and bills. These do not come through the migration import flow. Keep vendor bills in QBO unless you enter them manually in Conduit.
- Time tracking via QuickBooks Time. Conduit’s time tracking starts fresh. If you use QB Time today, decide whether to switch to Conduit’s time tracking or keep both.
- Tax tracking. Tax codes don’t transfer; Conduit applies a flat default tax rate from your company settings, override per-record.
- 1099 contractor tracking. Vendor 1099 status is a QBO concept, not a Conduit concept.
- Reports and report customizations. P&L, A/R aging, cash-flow reports get rebuilt in Conduit’s Analytics page from the imported data.
04After import
- Spot-check customers. QBO customer hierarchies (parent + sub-customers, or “jobs” inside customers) flatten. Verify a few of your customers display correctly.
- Verify items in pricebook. Open the Conduit Pricebook. Items should match QBO’s item list, organized by category.
- Connect Stripe in Settings → Payments for invoice collection.
- Decide on bidirectional sync. Open Settings → Integration Hub → QuickBooks to optionally enable Conduit invoices flowing back into QBO. Recommended for accounting reconciliation; covered in a separate guide.
- Adjust tax handling. QBO tax codes don’t transfer; set your default tax rate in Settings → Company Profile, override per-record where needed.
Run QBO and Conduit in parallel for at least a billing cycle to verify totals match.