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.
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.
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.
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 San Antonio, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The QuickBooks Online adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
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.