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.
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.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Lancaster, Pennsylvania. After go-live, the Sage Intacct 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.
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 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.
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.