How an insurance agency's customers, prospects, policies and X-dates in AMS360 can reach HubSpot, so producers and marketers can target coverage gaps, start renewals early and turn prospects into written business.
AMS360 is where the agency keeps its customers, policies and service work. HubSpot is where it markets, prospects and runs its sales pipeline. Producers need both: what each customer holds, what they are missing, and when the next policy or X-date comes up.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. The agency signs a Web Service SDK agreement or licenses Developer Portal access from Vertafore. The full API reference requires a Vertafore login.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
AMS360 exposes customers, policies and activities through Vertafore's APIs, so HubSpot can turn the agency's book into targeted marketing and timely renewals.
Campaign Creators assessment
Vertafore offers three ways in. The AMS360 Web Service API (WSAPI) is a SOAP interface that reads, adds and updates customers and limited policy data, with per-entity permissions set in AMS360. The Vertafore API Developer Portal provides REST and OData APIs for AMS360 with OAuth credentials, including activities, customer contacts, policy contacts and invoices. CC builds on whichever the agency licenses. Access is the gate: the Web Service SDK and Developer Portal access are both licensed from Vertafore, and the field list needs sign-off because AMS360 holds personal and policy data.
Ratings are CC judgments from Vertafore's public help and product materials. The full API reference sits behind Vertafore's login, so endpoints, fields and limits are confirmed during the credentials phase.
AMS360 types every record as a customer, prospect or suspect, and stores X-dates (coverage written elsewhere, with carrier, line and premium) on the customer. That is the raw material for agency marketing.
WSAPI covers customer and limited policy data. The REST and OData APIs cover activities, contacts, invoices and more. CC picks the interface per object, based on what the agency's license includes.
The agency signs a Web Service SDK agreement or licenses Developer Portal access from Vertafore, and approves which fields HubSpot may hold. Claims detail stays in AMS360.
Seven parts of AMS360 matter to HubSpot. Four carry the integration, two support it, and one stays inside AMS360 by design.
AMS360's SOAP interface. It retrieves, inserts and updates customer data, limited policy information, and lists of employees, business units and companies.
Every AMS360 record is typed as a Customer, Prospect or Suspect, and as an individual, family or business.
Written policies with line of business, writing and parent company, effective and expiration dates, status and premium.
Coverage the customer or prospect holds with another agent, recorded so the agency can quote before it renews.
Activities and follow-up work on the account. The Developer Portal shows an OData Post Activities method, and WSAPI supports activity and suspense integration.
REST endpoints documented in AMS360 release notes, including customer contact search by change date, policy contacts and invoice search.
Claims and customers marked as secured need explicit approval before any of their data reaches HubSpot.
AMS360 stays the system of record for customers, policies and accounting. HubSpot becomes the system of record for marketing, early prospects and the sales pipeline. A CC-built integration layer reads AMS360 changes, matches them to HubSpot records, applies the agency's data rules and writes in batches.
AMS360 owns customers, policies, premium and commission. HubSpot owns marketing data, early prospects and the sales pipeline until business is written in AMS360.
HubSpot keeps policy summaries, X-dates and line-of-business gaps. Documents, accounting and claim files stay in AMS360.
The agency signs off the field list. Secured customers and claims stay out unless approved, and the Marketing/Solicitation choice carries into HubSpot.
Each phase ends on a gate the agency signs off before the next begins. Read-only sync goes live first; write-back follows once the data is trusted.
Confirm what the agency licenses from Vertafore (Web Service SDK, Developer Portal APIs, OData), list the teams that will use HubSpot, and agree what each team should be able to do from it.
Create the WSAPI login with entity rights in the Administration Center, or register the application in the Developer Portal sandbox. Complete the agency's security review.
Agree how AMS360 records match into HubSpot (individuals and families to contacts, businesses to companies) and which fields HubSpot may hold.
Create the Policies custom object, properties, association labels, the new business and renewal pipelines and the ticket pipeline in a HubSpot sandbox.
Build the change reader, matching, data filter and batch writer for customers, contacts, policies and X-dates, with an error replay queue.
Load active customers, prospects, active policies and open X-dates. Then switch on write-back for new prospects and sales activities.
Build renewal, X-date, cross-sell and service workflows with sends paused, run two weeks in parallel, then switch on.
AMS360 fields are named as they appear in AMS360's screens and help. The matching API field names sit in Vertafore's gated reference and are confirmed during the credentials phase.
| AMS360 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers, prospects & suspects | ||||
| Customer ID | ams_customer_id | Company / Contact | AMS → HS | Primary match key. Unique. Confirm the API field in discovery. |
| Type (Customer, Prospect, Suspect) | lifecyclestage, ams_customer_type | Company / Contact | AMS → HS | Suspect to lead, Prospect to opportunity, Customer to customer. |
| Individual / Family / Business | Record type | Company / Contact | AMS → HS | Business to company; individual and family to contact. |
| Firm Name, DBA | name, ams_dba | Company | AMS → HS | Commercial accounts. |
| First, Last | firstname, lastname | Contact | ↔ Both | Fill blanks only; AMS360 wins on conflict. |
| Contact | ↔ Both | Secondary match key. | ||
| Marketing/Solicitation | ams_marketing_ok | Contact | AMS → HS | Respected in HubSpot marketing lists. |
| Executive | hubspot_owner_id | Company / Contact | AMS → HS | Account executive becomes owner. Confirm the role mapping. |
| Representative | ams_csr | Company / Contact | AMS → HS | Customer service rep as a user property. |
| Division, Branch, Department | ams_branch | Company / Contact | AMS → HS | For team views and reports. |
| Business Origin | ams_business_origin | Company / Contact | AMS → HS | |
| Policies | ||||
| Policy # | ams_policy_number | Policy (custom object) | AMS → HS | Policy match key with the customer ID. |
| Line of Business | ams_line_of_business | Policy | AMS → HS | Mapped to a short category list. |
| Writing Company | ams_carrier | Policy | AMS → HS | Carrier. |
| Eff/Exp Date | ams_effective_date, ams_expiration_date | Policy | AMS → HS | Expiration drives renewal deals and tasks. |
| Status | ams_policy_status | Policy | AMS → HS | Confirm status values in discovery. |
| Premium | ams_premium | Policy | AMS → HS | Rolled up per customer in the integration layer. |
| Exec, Rep | Associated owner | Policy | AMS → HS | Primary service group on the policy. |
| X-Dates | ||||
| X-Date | ams_xdate | Policy (X-date) | AMS → HS | Expiration of coverage held elsewhere. |
| Company, Current Agent | ams_carrier, ams_current_agent | Policy (X-date) | AMS → HS | |
| Line of Business | ams_line_of_business | Policy (X-date) | AMS → HS | |
| Premium, Interest Level | ams_premium, ams_interest_level | Policy (X-date) | AMS → HS | Prioritizes producer outreach. |
| Activities & service | ||||
| Activity (open) | Task or Ticket | Task / Ticket | AMS → HS | Service requests become tickets; follow-ups become tasks. |
| HubSpot call, meeting, email | Activity | AMS360 Activity | HS → AMS | Logged on the AMS360 customer so service staff see sales touches. |
| Qualified HubSpot lead | Prospect | AMS360 customer | HS → AMS | Created as a Prospect when sales-qualified. |
Vertafore grants API access under a license. Values Vertafore does not publish are marked for confirmation.
| Topic | AMS360 | HubSpot |
|---|---|---|
| Access model | Web Service SDK agreement with Vertafore for WSAPI; Developer Portal access as a licensed customer, with the APIs and scopes the agency contracted. | Self-serve in the agency's portal. Custom objects need an Enterprise subscription. |
| Interfaces | WSAPI (SOAP) for customers and limited policy data; REST and OData APIs through the Vertafore API Developer Portal. | REST APIs: CRM objects, associations, pipelines, custom objects, imports. |
| Authentication | WSAPI: a login ID and password per integration user, created in the AMS360 Administration Center. Developer Portal: OAuth credentials for AMS360. | Private app access token or OAuth 2.0 app, scoped per object. |
| Permissions | WSAPI rights set per entity (retrieve, add, update, delete). API users can be limited by security group; access to secured customers is a separate admin grant. | Field-level permissions and teams control who sees premium and commission. |
| Testing | WSAPI test environment with sample data; Developer Portal sandbox, promoted to Live by Vertafore. | HubSpot sandbox portal for schema and workflow testing. |
| Rate limits | Not published. Confirm with Vertafore. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Personal data, policy detail and claims. Secured customers restrict employee access. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
The Web Service SDK and Developer Portal access are licensed from Vertafore. Make the license and credentials a client-owned dependency in the SOW, with a date.
AMS360 holds personal details and policy information. The agency approves the field list, claims stay out, and secured customers are excluded unless approved.
Vertafore's full API reference sits behind its login. Budget a short discovery spike to confirm endpoints and fields once credentials are issued.
WSAPI's policy coverage is limited. Where the agency licenses the Developer Portal APIs, CC uses them for the policy and activity detail WSAPI does not cover.
Each agency sets up its own lines. CC maps them into a short list of HubSpot categories so cross-sell reports stay readable.
A WSAPI user is locked out for twenty minutes after five failed logins. The integration alerts on authentication errors instead of retrying blindly.
Every X-date becomes a HubSpot record with a date, so nurture emails and producer calls start well before the coverage renews elsewhere.
Customers with auto but no home, or property but no umbrella, land in HubSpot lists automatically, by producer and by branch.
Each expiring policy creates a renewal deal and tasks a set number of days out.
Imported suspects are nurtured in HubSpot and promoted to Prospect in AMS360 once they qualify.
Requests from forms, email or chat become HubSpot tickets and are logged on the AMS360 customer.
Premium by line, producer and branch sits next to pipeline and campaign results in HubSpot dashboards.
AMS360 already tracks how far each record is from being a customer. The integration lets HubSpot move each one forward with marketing and sales work, while AMS360 keeps the written business.
All custom properties use the ams_ prefix in an AMS360 property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ams_customer_id | AMS360 Customer ID | Company / Contact | Single-line text | Customer key; unique |
| ams_customer_type | AMS360 Type | Company / Contact | Dropdown | Customer, Prospect, Suspect |
| ams_marketing_ok | Marketing/Solicitation | Contact | Single checkbox | From Customer Setup |
| ams_csr | AMS360 Representative | Company / Contact | HubSpot user | Representative role |
| ams_branch | AMS360 Branch | Company / Contact | Dropdown | Division / Branch / Department |
| ams_total_premium | Total Premium | Company / Contact | Number (currency) | Sum of active policy premium |
| ams_next_expiration | Next Expiration Date | Company / Contact | Date picker | Earliest expiration on active policies |
| ams_lob_gaps | Cross-sell Gaps | Company / Contact | Multiple checkboxes | Agreed lines not held |
| ams_policy_number | Policy Number | Policy | Single-line text | Policy # |
| ams_line_of_business | Line of Business | Policy | Dropdown | Line of Business mapped to categories |
| ams_xdate | X-Date | Policy | Date picker | X-Date section of Customer Setup |
| ams_interest_level | Interest Level | Policy | Dropdown | Closed, High, Medium, Low |
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the agency.
Based on public documentation. Each item marked for confirmation is verified with Vertafore and the agency during the credentials phase.
Yes, through a custom build on Vertafore's APIs: the AMS360 Web Service API (SOAP) and the REST and OData APIs in the Vertafore API Developer Portal. Access is licensed by Vertafore, so the agency signs a Web Service SDK agreement or licenses Developer Portal access, and Campaign Creators builds on whichever the agency has.
AMS360 customers, prospects and suspects sync to HubSpot companies and contacts with a matching lifecycle stage, and policies and X-dates sync to a Policies custom object with line of business, carrier, dates and premium. HubSpot sends new prospects and sales activities back to AMS360.
AMS360 owns customers, policies, premium and commission. HubSpot owns marketing data, early prospects and the sales pipeline until business is written in AMS360. Claims and secured customers stay out of HubSpot unless the agency approves them.
Seven phases, each closed by an agency sign-off: discovery and license, credentials and sandbox, identity and data rules, the HubSpot data model, the inbound sync build, backfill and write-back, and a two-week parallel run before renewal, X-date and cross-sell workflows are switched on.
Timeline and cost depend on the Vertafore APIs the agency licenses, the records and fields in scope, and whether write-back is included. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.