Management gets visibility and control. Producers get their time back. Epic runs your back office; Salesforce is where your team sells and serves.
Every policy, premium, carrier, and renewal visible in Salesforce in real time. No waiting on an Epic report to know where the agency stands.
Producers, splits, and earned commissions come across from Epic, so you can watch revenue develop right alongside the policies that generated it.
Claims activity, servicing status, and renewal timelines surface on every account, so at-risk clients show up before they become lost clients.
Every record that moves is logged in plain English. Write-back to Epic stays off until you enable it, and Epic remains your system of record.
Clients, contacts, and policies arrive from Epic automatically and stay in step. The busywork disappears, and so do the transcription errors.
Policies, coverages, claims, and certificates sit on the client record you already work in. Walk into every call knowing the whole relationship.
Carrier submissions show submitted, quoted, and bound status right on the opportunity. Know where your deals stand without chasing the service team.
Your commissions and splits are visible next to the policies that earned them, so renewal value and payout are never a mystery.
Built on standard Salesforce Financial Services Cloud objects, so your Epic data lands in the records your team already uses, not in a bolted-on system.
All install and testing happens in a full-copy Salesforce sandbox (a replica of your live org) first. We only promote to your live org once you've approved what you've seen.
The integration is delivered with write-back to Epic switched off. It begins by pulling Epic data into Salesforce; sending anything back to Epic is a separate, deliberate switch you turn on only when you're ready.
This integration is designed for Financial Services Cloud for Insurance Brokerages, Salesforce's insurance-broker edition of FSC. That's what provides the insurance-specific data models (clients, policies, carriers, producers, commissions) the integration maps Epic data into.
The good news: for existing FSC customers, the Insurance Brokerage capability is a $0 add-on SKU, with no additional license cost to enable it.
A broad, continuous flow from Epic into Salesforce, and a precise, deliberate flow back. Epic stays your system of record.
Runs automatically on a schedule. Records are matched on Epic's own IDs, so re-syncing updates existing records instead of creating duplicates.
| From Epic | Appears in Salesforce as |
|---|---|
| Clients (your customers) | Accounts: individuals as person accounts, businesses as business accounts |
| Contacts (people at those clients) | Contacts, linked to the right account |
| Companies / carriers | Carrier accounts, referenced on the policies they write |
| Policies | Insurance Policy records |
| Policy lines & coverages | Coverage detail on each policy (limits, premiums, line of business) |
| Claims | Claim records on the policy |
| Certificates & documents | Files attached to the right record, classified by type |
| Servicing status & renewal timeline | The policy's current service status and renewal lineage |
| Activities / notes | Activity history on the client and policy |
| Producers & servicing roles | Producer records |
| Commission splits / arrangements | Split arrangements tied to the policies that generated them |
| Commissions (statements + detail) | Commission statements and per-producer commission records |
| Marketing submission status | Live status (submitted → quoted → bound) on the opportunity |
Precise by design and fully logged. Each action is enabled deliberately; nothing goes back to Epic silently.
| From Salesforce | Becomes in Epic |
|---|---|
| A new client (new Account) | A new client record created in Epic |
| A client/contact detail change (e.g. phone, address) | An update to the matching Epic client or contact |
| A marketing submission (from an Opportunity) | A marketing submission created in Epic |
| A completed service Task | An activity created in Epic, attached to the client, policy, claim, or case |
Epic data arrives on a schedule you control. Changes made in Salesforce head to Epic the moment you save.
Scheduled poll: you set the cadence, and can also trigger an immediate refresh on demand ("Run Sync") without waiting for the next scheduled run. Each run pulls only what's new or changed since the last one.
Triggered by the record change: captured the instant you save, sent to Epic within seconds to a few minutes. Near-real-time, deliberately just short of instant.
Every sync is recorded and anything that needs attention is easy to find and quick to fix. No support tickets, no guesswork.
Every push and pull is written to an audit log with a plain-English status and a link to the record. One odd record never holds up the rest of the sync.
The Sync Admin dashboard shows health at a glance, with one-click Retry. Green / amber / red badges on each client, contact, and policy show it's in step, right where your team works.
Fix the cause, re-run, done. The sync matches on Epic's own IDs and rewrites only what changed, and outbound sends retry automatically.
Your entire book loads once, in the right order, as a first-class part of the project. Then the ongoing sync takes over.
Before anything is created, a reconciliation pass matches records you already have in Salesforce to their Epic counterparts on natural keys and links them. The load updates those records instead of creating a second copy.
A large book loads gradually over hours, deliberately throttled, not in one risky blast. If paused or interrupted, it resumes exactly where it left off, with a live progress screen and an operator stop control throughout.
Every record loaded, and anything that couldn't be, is written to the audit trail, so verifying the migration is a matter of comparing counts and reviewing a short list of exceptions.
PS Advisory does the technical work; we only need a few specific things from you and from Applied along the way. Nothing touches your live systems until you've seen it working safely in a test environment first.
We install the PS Advisory Applied Epic connector into your Salesforce org: the connection layer, sync engine, audit trail, and on-screen status indicators. Your data model stays clean.
What we need: A Salesforce org on Financial Services Cloud for Insurance Brokerages, and a Full sandbox with admin access for the install.
We assign access, load the Applied credentials into Salesforce's encrypted credential store, set your sync schedule, and confirm every safety switch before anything runs.
What we need: Your preferred sync frequency, plus a short working session to capture your agency-specific Epic codes.
Applied provides API access through the Applied Dev Center. You make the request; we give you a checklist with the exact wording to forward to your Applied rep.
What we need: This is usually the step with the longest lead time, so it's worth starting early.
You hand us the Applied credentials; we load them securely into Salesforce and run a live verification pull to prove the whole chain works end to end, before any real data is involved.
What we need: The Applied credentials, and an early request to Applied for a full Applied Epic sandbox.
Clients, contacts, carriers, policies with their coverages and premiums, claims, certificates and documents, producer commissions and splits, servicing status, renewal timelines, and activity history flow from Applied Epic into Salesforce Financial Services Cloud on a schedule you control, and stay in step automatically.
Yes, but only deliberately. Changes made in Salesforce can flow back to Epic the moment they are saved, and every write-back action ships switched off, is enabled intentionally, and is fully logged. Epic remains your system of record; nothing goes back to Epic silently.
The integration is built on Salesforce Financial Services Cloud's insurance data model, which represents policies, coverages, claims, and producer relationships as first-class records. FSC for Insurance Brokerages is available at no additional license cost for qualifying agencies, and PS Advisory handles the setup.
A built-in migration loads your entire book once, in dependency order: clients, then contacts, then policies, then coverages. It is a first-class part of the project, not a spreadsheet exercise. After the initial load, the ongoing scheduled sync takes over.
Setup follows four steps: PS Advisory installs the connector in your Salesforce org, configures access and the sync schedule, you request API access from Applied through the Applied Dev Center using the checklist we provide, and we verify the connection end to end against real data before anything touches your live org. Applied's production approval typically takes 2 to 5 business days.
Yes. Applied credentials live in Salesforce's encrypted credential store, never in code or documents. Everything runs on standard Salesforce security, every record that moves in either direction is logged with a plain-English status, and Applied Epic remains your authoritative back-office system throughout.
Test against real data in a sandbox, promote to your live org once you've approved what you've seen, then switch on write-back if and when you want it. Every step visible, every record audited.
Standard FSC Objects
No bolted-on data model
Fully Audited
Every record logged, both directions
Fail-Closed Safety
Write-back off until you say so