Does it work with our existing QuickBooks Online licenses?
Yes — the adapter rides on top of your existing QuickBooks Online subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Do we own the integration code at the end?
Yes. The Connectify QuickBooks Online adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
How long does the QuickBooks Online integration take to ship?
Our standard window is thirty days from signed scope to live QuickBooks Online adapter in production, plus a one-week monitored stabilization phase. For Syracuse, New York, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Can the QuickBooks Online adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your QuickBooks Online tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
What happens if QuickBooks Online changes their API after we go live?
Our SRE team monitors QuickBooks Online change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Syracuse, New York. After go-live, the QuickBooks Online adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.