Migrate from Stames to HubSpot Service Hub

Stames Tickets map directly to HubSpot Tickets. We preserve ticket status, priority, assignment (hubspot_owner_id resolved to HubSpot User), created_at and updated_at timestamps, and any SLA metadata as custom fields. Stames Ticket channel source is preserved in a custom HubSpot property for reporting. The customer confirms the status mapping matrix during scoping because Stames statuses are customer-defined and do not have a standard enum. Reminders and notification metadata on Tickets export as custom fields for manual post-migration validation.

Stames Conversations are threaded message records attached to Tickets. We export the full message history including agent and customer messages, timestamps, channel attribution, and internal notes. Each message maps to a HubSpot conversation message record, preserving threading order by created_at timestamp. Channel attribution from Stames (Facebook, Instagram, WhatsApp, Email, API, Contact Forms) is preserved as a channel property on each message so reports can filter by original channel source.

Stames Customer records map to HubSpot Contacts. We preserve contact name, email, phone, and any metadata fields. Stames stores an implicit account reference on Customer records that we resolve as a HubSpot Company during migration. Customers without an associated account are imported as standalone Contacts and flagged for the customer admin to associate post-migration.

Stames User and Agent accounts with role and permission metadata map to HubSpot Users. We resolve agents by email match against the destination HubSpot portal User table. Permission equivalence is evaluated during discovery; HubSpot's roles and permissions model differs from Stames, and permission gaps are flagged in the scoping document for the customer admin to configure post-migration.

Tags applied to Stames Tickets for categorization export as HubSpot Ticket Labels. Tag naming is preserved and mapped directly. If the customer uses tags for multi-dimensional categorization, we apply them as multiple Label associations on the HubSpot Ticket object.

Stames aggregates messages from Facebook, Instagram, WhatsApp, Email, API, and Contact Forms. Each source channel is stored as a field on the Conversation record. We map channel attribution explicitly as a HubSpot custom property on the conversation so that reporting can filter by original channel. HubSpot natively supports Facebook and WhatsApp channels; Email and Contact Form map to HubSpot's Email and Inbox channels respectively.

Stames built-in SMS and Email reminder and notification system metadata attaches to Tickets as fields. We export these as custom properties on the HubSpot Ticket record for post-migration review. The notification triggers themselves cannot be migrated; HubSpot SLA policies and workflow automations on Service Hub Professional and above provide the equivalent SLA enforcement and escalation capability, and we document the recommended configuration during the automation inventory handoff.

File attachments on Stames Tickets and Conversations are downloaded and re-uploaded to HubSpot Files storage. We preserve filename, file size, upload timestamp, and the association to the parent Ticket. Media URL references from Stames update to point to the new HubSpot file location. If Stames stores attachments externally, we verify the download URL during the export phase before scheduling re-upload.

Stames self-service portal configurations including custom forms, portal access controls, branding settings, and portal-facing content are not exposed via the Stames API. We do not migrate portal configurations. This is communicated explicitly during discovery. The customer must recreate portal settings in HubSpot Service Hub manually post-migration. We document the Stames portal structure observed during export so that the admin has a reference when rebuilding.

Stames custom fields on Tickets map to HubSpot Ticket custom properties. We evaluate field type compatibility during schema design: text fields map to single-line text, number fields map to number, date fields map to date-time, checkbox fields map to booleans, and dropdown fields map to HubSpot single-option or multi-option properties. Stames custom fields with unsupported types are flagged for the customer to decide on a HubSpot equivalent.

Stames custom fields on Customer records map to HubSpot Contact custom properties using the same type-mapping logic applied to Ticket custom fields. If any Stames Customer custom field references a related entity (such as a company or product), we resolve the reference to the corresponding migrated HubSpot record during import.

Stames may store an implicit organizational record on Customer or Ticket. If the source Stames instance contains a distinct company or organization object, we map it to HubSpot Companies. The HubSpot Company becomes the parent association for related Contacts, enabling account-level reporting and ticket grouping by organization in HubSpot Service Hub.