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.
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.
Is this a packaged Sage Intacct 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.
What happens if Sage Intacct changes their API after we go live?
Our SRE team monitors Sage Intacct 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.
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 Peoria, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
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.