AMS Integrations

Sync your book of business from your agency management system

AMS Integrations

BindPilot integrates with major agency management systems to sync clients and policies, keeping your data in sync.

Supported AMS Platforms

| AMS | Status | Features | |-----|--------|----------| | AMS360 | In development | Sync clients, policies, renewals | | Applied Epic | In development | Sync clients, policies, renewals | | HawkSoft | In development | Sync clients, policies | | EZLynx | Planned | — | | Custom (CSV) | Live | Manual import/export via CSV |

Setting Up AMS Integration

AMS360

  1. Go to Settings > Integrations > AMS360
  2. Click Authorize
  3. Authorise BindPilot from your AMS360 account (OAuth — you sign in to AMS360 directly, not to BindPilot)
  4. Approve scopes (clients, policies, renewal dates)
  5. BindPilot begins syncing (takes 5–15 minutes for typical book)

Two-way sync (Q3): Future updates will allow you to update renewal dates and client info in BindPilot and push changes back to AMS360.

Applied Epic

  1. Go to Settings > Integrations > Applied Epic
  2. Click Authorize
  3. Authorise BindPilot from your Applied Epic account (OAuth)
  4. BindPilot syncs your clients and policies

Sync direction: AMS → BindPilot, read-only. BindPilot does not write back to your AMS. Two-way sync is on the roadmap, undated.

HawkSoft

  1. Go to Settings > Integrations > HawkSoft
  2. Click Authorize
  3. Approve API access
  4. Initial sync begins (can take 10–30 min for larger books)

Renewal Data: Renewal date sync is in development.

Sync Behavior

Initial Sync

First sync imports your entire book of business:

  • Clients (name, address, contact info)
  • Policies (type, coverage, premium, expiration date)
  • Carriers (policy carrier, effective/expiration dates)

Takes 5–30 minutes depending on book size (50–5000+ policies).

Ongoing Sync

After initial sync, BindPilot checks for updates:

  • Frequency: Every 6 hours
  • Updates: New policies, client changes, renewal dates
  • Conflicts: If same policy exists in BindPilot and AMS (with different data), AMS data wins

Best Practice: Don't manually edit AMS-synced data in BindPilot; edit in your AMS, and BindPilot picks up changes.

Policy Matching

BindPilot matches policies between your AMS and BindPilot using:

  1. Carrier + policy number (exact match)
  2. Carrier + client + coverage type (fuzzy match)

If a match fails, the policy appears as a duplicate. Alert your support team to merge.

Stopping a Sync

To stop syncing with an AMS:

  1. Go to Settings > Integrations > [AMS Name]
  2. Click Disconnect
  3. Historical data is archived but no longer synced

You can re-authorize anytime to resume.

CSV Import/Export

If your AMS is not supported, use CSV import:

  1. Go to Clients > Bulk Import
  2. Download the template CSV
  3. Fill in your client/policy data
  4. Upload CSV; BindPilot imports and creates clients

See CSV Import/Export for format details.

Data Privacy & Security

  • BindPilot stores only the data your AMS syncs (no direct database access)
  • Your AMS password is never stored — authorisation is via OAuth, and BindPilot holds only the resulting token, which you can revoke from your AMS at any time
  • Data syncs over encrypted HTTPS
  • 30-day automatic cleanup of revoked integrations

Next: Set up webhooks for real-time event notifications.

Last updated: Recently