Migrate from ASAPP to HubSpot Service Hub

ASAPP Conversation records map to HubSpot Service Hub Tickets. Each ticket receives the conversation thread as a series of ticketPipeline comments, with the conversation channel (messaging, voice, digital) stored as a custom ticket property. Resolution outcome from ASAPP maps to Ticket Status. We reconstruct the full conversation timeline by querying all three ASAPP export channels (S3 batch, File Exporter API, real-time event API) and merging them chronologically to eliminate gaps between batch windows.

ASAPP's conversation threads migrate as HubSpot conversations in the shared inbox. Message-level metadata including timestamp, direction (inbound/outbound), agent identifier, and channel type map to conversation message properties. CSAT scores from ASAPP conversation metadata transfer to a custom ticket property for SLA and quality reporting in HubSpot.

ASAPP Agent records map to HubSpot Users with the agent's performance metrics (handle time, resolution rate, CSAT) stored as custom User properties. Agent team assignments in ASAPP map to HubSpot Teams so that ticket routing rules in HubSpot can replicate the routing logic documented during discovery. Agent identity is resolved by email match during migration.

ASAPP Customer profiles associated with conversations map to HubSpot Contacts with the customer identifier preserved in a custom Contact property. Where ASAPP records organizational context alongside the customer profile, we create a corresponding HubSpot Company record and link it to the Contact via the association. Customer-level properties migrate as Contact properties.

ASAPP custom structured-data fields are defined via the structured-data-field API and vary per deployment. We export the full field schema before migration and create equivalent HubSpot custom properties. Field type mismatches (ASAPP extracts structured text from conversations that may not map directly to typed HubSpot fields) are flagged for customer review. If the customer has more than 10 custom fields and uses them as independent record types, we recommend HubSpot Enterprise custom objects as the destination.

ASAPP Segments define which structured data the system extracts for specific conversation types and are configurable via the segments API. Segment definitions migrate as HubSpot Lists (for audience segmentation) or as custom Contact properties (for conversation-type tagging) depending on the customer's reporting goals. The segment-to-field association migrates as a custom property value rather than a structural object.

ASAPP File Exporter API reports contain agent performance, conversation volume, CSAT, and channel metrics. These reports are not native HubSpot report types, so we import the report data as custom HubSpot properties on the relevant objects (Agent, Ticket, Contact) and document the metric definitions for the customer to configure HubSpot-native reports as equivalents. Report configuration is out of migration scope; we deliver the metric mapping specification.

ASAPP S3 batch reports contain historical conversation volume and aggregate metrics with predictable time delays. We import S3 batch data as Ticket records with historical timestamps to preserve the reporting timeline in HubSpot. Batch delay is documented as a data-latency caveat in the migration scope agreement.

ASAPP real-time event API data migrates as the most recent Ticket records with current timestamps. The real-time channel is used to capture any conversations that fall outside the S3 batch window. We query the real-time API last to capture the final delta before cutover.

ASAPP conversation metadata (channel type, routing information, CSAT scores, disposition, escalation flags) migrates as custom Ticket properties in HubSpot. Channel type maps to a HubSpot ticket property; CSAT maps to a numeric ticket property for SLA reporting. Escalation flags become custom ticket properties that can trigger HubSpot workflows post-migration.

ASAPP's GenerativeAgent tuning, routing rules, intent configurations, and AI model settings are proprietary platform settings stored in ASAPP's infrastructure, not exported via API. We do not migrate these as data. We perform a full discovery inventory of every AI configuration, routing rule, and intent model during the discovery phase and deliver a written requirements specification that the customer's HubSpot admin uses to configure Breeze AI and workflow rules in HubSpot Service Hub Enterprise.

ASAPP engagement records (calls logged within conversations, emails, meeting metadata) map to HubSpot Ticket engagement records. Call duration and disposition migrate as custom engagement properties. Meeting metadata (attendees, timestamp, outcome) migrates as HubSpot meeting engagement records linked to the parent Ticket. Tasks associated with conversation follow-up migrate as HubSpot Tasks attached to the Ticket.

If the ASAPP deployment includes custom object records created via the structured-data-field API (beyond simple custom fields), these map to HubSpot Custom Objects. Custom Objects require HubSpot Service Hub Enterprise ($150/seat/mo). We pre-create the destination schema including all custom properties and relationships in the customer's HubSpot portal before migration and validate the schema in a test environment before production import.