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.
Is this a packaged QuickBooks Online connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
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.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the QuickBooks Online surface.
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.
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.