How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Sage Intacct 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 Sage Intacct adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Sage Intacct tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Does it work with our existing Sage Intacct licenses?
Yes — the adapter rides on top of your existing Sage Intacct 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 Sage Intacct surface.
How long does the Sage Intacct integration take to ship?
Our standard window is thirty days from signed scope to live Sage Intacct adapter in production, plus a one-week monitored stabilization phase. For Mount Vernon, New York, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Do we own the integration code at the end?
Yes. The Connectify Sage Intacct 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.