Is this a packaged Salesforce 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.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Salesforce adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What happens if Salesforce changes their API after we go live?
Our SRE team monitors Salesforce 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.
Can the Salesforce adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Salesforce tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
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 Salesforce surface.
How long does the Salesforce integration take to ship?
Our standard window is thirty days from signed scope to live Salesforce adapter in production, plus a one-week monitored stabilization phase. For Houston, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.