Connecting Applied Epic to Salesforce: The Real Story

If you’re running Applied Epic and thinking about adding Salesforce, the first question is always: how do these two systems talk to each other? We work with agencies at both ends of that journey: ones doing this for the first time, and ones that have been running the connector for a while and are running into problems. This post covers both paths, what they actually cost, and the things nobody tells you upfront.

Why Agencies Want This Integration

Most agencies we work with have the same setup. The servicing team lives in Applied Epic and it does that job well. Policies, claims, renewals, carrier submissions. It’s all in there. But the sales side is struggling. There’s no good way to manage pipeline, track leads, or run marketing out of Epic. So someone decides to bring in Salesforce.

That’s the right call. The question is how you connect the two. Get it wrong and you end up with duplicate data entry, broken handoffs between sales and service, and two systems that are technically connected but practically a mess.

Two Paths: The Connector vs. Custom Integration

There are two ways to connect Applied Epic and Salesforce. The first is Applied’s own connector product. The second is a custom integration built on the Epic API. We’ve done both, and for most agencies we recommend the custom route. Here’s what each option actually involves.

Path 1: Applied Epic for Salesforce (AESF) Connector

Applied Systems sells a managed package called Applied Epic for Salesforce. It installs directly into your Salesforce org and handles the sync between the two systems. There’s a lot going on under the hood, but from a user perspective it’s designed to work out of the box.

What you get:

• Accounts, contacts, opportunities, policies, activities, and attachments syncing between both systems
• Support for Business Accounts and Person Accounts
• An optional Financial Services Cloud extension if you’re using FSC
• Applied Epic manages the integration infrastructure, but you’re still expected to resolve any sync issues, handle upgrades to the application, and deal with general maintenance

What to watch out for:

• Every user who needs the integration requires both a Salesforce license and an Applied Epic license, plus Applied’s per-user connector fee on top. That adds up quickly as your team grows.
• Data doesn’t start flowing into Epic until a lead converts to an opportunity in Salesforce
• Some fields only sync one way, and some don’t sync at all. You don’t get to change that
• You need Applied’s professional services team to install and configure it. This isn’t a self-serve setup
• The sync isn’t real-time. Changes in one system can take time to appear in the other, which means your team may be working from data that’s already out of date.
• Customization is more limited than you’d expect from a product at this price point
• Support goes through Applied Epic, and in our experience the connector isn’t their primary focus. Their core business is the AMS, not the integration layer. That means support requests can be slow and feature gaps don’t always get addressed quickly.

Path 2: Custom Integration via Middleware

The alternative is building your own integration using middleware like MuleSoft or Salesforce Apex code, connecting directly to Applied Epic’s REST APIs. You control what syncs, when, and how.

What you get:

• Full control over what data moves, when it moves, and how it’s mapped
• No per-user connector fees and your Salesforce users don’t need Applied Epic licenses. You can scale to thousands of users without the licensing costs stacking up the way they do with the per user connector
• The ability to connect other systems beyond just Epic and Salesforce
• An integration you can actually change as your business evolves

What to watch out for:

• The build takes more time since everything is being done to your specific requirements
• You control the maintenance, upgrades, and new features. You’re not waiting on Applied Epic’s roadmap to make things happen.
• You need a partner who understands both the Epic API and the Salesforce data model

What Syncs and What Doesn’t

	Connector	Custom
Sync timing	Batch, not real-time	Real-time or scheduled
What syncs	Fixed by Applied	You decide
Claims data	No	Yes
Data retention control	Applied controls	You control
Policy object location	Applied’s custom object	FSC or custom
Renewal pipeline	Stays in Epic	Optional: run through Salesforce
Who can see the data	Connector license required	Any Salesforce user

With the Applied Epic Salesforce Connector

• The point at which data flows into Epic is fixed. It happens at lead conversion in Salesforce, and Applied Epic controls that. Depending on your sales process, that might be too early or too late, but you can’t change it.
• Not all objects sync, and not all fields sync. Claims data, for example, stays in Applied Epic and doesn’t come across to Salesforce. For the objects that do sync, some fields are one-way, some are bidirectional, and some don’t sync at all. None of that is configurable.
• You can’t control the retention period or time range of data that syncs across. The connector determines that. You may end up with ten years of policy history in Salesforce whether you need it or not, which can consume significant storage.
• Policy data is stored in Applied Epic’s own custom object inside Salesforce. Only users with a connector license can access it. If a Salesforce user doesn’t have a connector license, they can’t see the policy data at all.

With a Custom Integration

• You choose what syncs and what doesn’t. Only want the last two years of policy data? Done. Only want active policies? Done. You’re not pulling across data you don’t need.
• Any data from Applied Epic can come across, not just what the connector supports. Claims, custom fields, legacy data points — if it’s in Epic, we can bring it into Salesforce. We also handle any transformation along the way, so the data arrives in the format your reports and dashboards actually need, not just how Epic stores it. And where Applied Epic’s functionality has gaps or limitations, we can build on top of it. Custom views, additional automation, logic that the connector simply doesn’t support.
• You choose where the data lives in Salesforce. Whether you’re using Financial Services Cloud or your own custom objects, the integration maps to whatever model fits your org. You’re not locked into the object structure Applied Epic dictates.
• Every Salesforce user can see the data. There’s no per-user license gate on who can access what. If someone has a Salesforce license, they can see the data.
• You control the sync direction and timing. Real-time, batch, scheduled — and you decide which system wins when there’s a conflict.
• You can connect other systems at the same time. If you’re also integrating a rating tool, a billing system, or a claims platform, the same middleware handles it all.
• Renewal opportunities can run through Salesforce. With a custom integration, your renewal pipeline lives in Salesforce alongside new business. Your producers work one system, not two.

Two Components We Recommend for Every Integration

Once your data is syncing, there are two custom Lightning Web Components worth adding. They’re not part of either integration option out of the box, but we recommend them to every agency we work with. Both give your team a noticeably better experience working with Epic data inside Salesforce.

Attachments

If you want Salesforce users to see Applied Epic documents, you need a custom LWC to pull files from the API and display them on the relevant Salesforce record. Files stay stored in Epic so you’re not eating into your Salesforce storage, and your team gets a clean, searchable file view without ever leaving Salesforce.

Activities

Applied Epic activities sync over, but each one can carry multiple notes that you’d have to open individually to read. This component surfaces the activity and all its associated notes in one view, so your account managers can see the full picture at a glance.

Pricing Calculator

Put your numbers in and see how the two paths compare over time.

For most agencies, the math favors custom once you factor in the long-term connector licensing, the sandbox refresh fees, and the cost of working around the connector’s limitations.

Implementation: What to Expect

Connector Timeline

Plan for a minimum of 12 weeks:

1. Purchase connector licenses from Applied
2. Install the managed package into your Salesforce sandbox
3. Applied turns on API access on their side
4. Configure field mappings and sync settings (with Applied PS)
5. Test the full cycle: lead creation, conversion, opportunity sync, Epic sync, and data flowing back
6. Validate data accuracy, permissions, and user access
7. Deploy to production

You’ll need access to both a Salesforce sandbox and an Applied Epic test environment running simultaneously.

Custom Integration Timeline

Expect 3 to 5 months as this is a custom build to your specifications:

1. API credential setup and authentication
2. Data model mapping between systems
3. Middleware development and configuration
4. Sync logic (real-time vs. batch, conflict resolution)
5. Error handling and monitoring
6. Testing with production-like data volumes
7. Phased rollout (usually accounts/contacts first, then policies, then activities)

Either way: Start with the most critical data. For most agencies that means accounts and contacts first, then opportunities, then policies, then activities and attachments. Don’t try to sync everything on day one.

Where HipTen Fits

We’re a Salesforce implementation partner that works exclusively with insurance companies. That means we’ve seen the Applied Epic integration from every angle: the connector path, the custom path, and the “we tried the connector and now want to switch” path.

We understand both the Salesforce data model and how insurance agencies actually operate in Epic. That combination matters because the hardest part of this integration isn’t the technology. It’s making the right design decisions about what data goes where and how your teams will actually use both systems together.

If you’re evaluating your options, get in touch. We’ll tell you honestly which path makes sense for your agency and what it will actually take to get there.