Migrate from Locobuzz to HubSpot Service Hub

Locobuzz Tickets map directly to HubSpot Service Hub Tickets. The ticket subject, description, status (open, pending, resolved, closed), priority (low, medium, high, urgent), channel origin (social, messaging, email, review), assigned agent (hubspot_owner_id resolution), SLA deadline, and tag associations all migrate as structured fields. Conversation threads migrate as threaded ticketPipeline entries attached to the Ticket. The mapping resolves the Locobuzz ticket ID as a custom field locobuzz_ticket_id__c for audit trails.

Locobuzz Customer profiles (name, email, phone, social handles, messaging channel identifiers, interaction history) map to HubSpot Contact records. Social handle fields (Twitter handle, Facebook ID, Instagram username) migrate as custom contact properties. Channel identifiers are preserved as custom fields to support any routing logic the customer uses in HubSpot workflows. A Contact is created before the first Ticket import so that the Ticket.associatedContactId lookup is satisfied.

Locobuzz Company records (brand name, domain, escalation contacts, brand-level SLA settings) map to HubSpot Company records. The Locobuzz company domain becomes the Company Website field and is used as a dedupe key during import. Some Locobuzz customers use only individual Customer records without explicit Company grouping; we ask scoping questions to determine whether the customer uses company-level records or only contacts. Companies are migrated before Contacts to satisfy the Company-Contact association.

Each Locobuzz Ticket contains a chronological conversation thread with agent responses, customer replies, internal notes, and attachments across channels. We export the full thread and attach it to the HubSpot Ticket as conversationPipeline entries preserving timestamp, author (agent vs customer), message body, and attachment references. Inline images are re-attached as HubSpot file attachments linked to the ticket record.

Locobuzz aggregates Reviews from Google My Business, industry platforms, and social sources with rating, source platform, sentiment score, response status, and brand response history. HubSpot Service Hub has no native review monitoring equivalent. We migrate review records as HubSpot Tickets with a custom object or custom field set: review_source (select), review_rating (number), review_sentiment (text from Locobuzz AI layer), response_status (checkbox), and review_response_body (long text). This preserves the review data in HubSpot for reference without requiring a separate review monitoring tool.

Locobuzz Agent records (name, email, role, team assignment, active/suspended status) map to HubSpot User records. We match by email address during migration. Any HubSpot User provisioned with the same email as a Locobuzz agent inherits the agent's ticket assignments. Suspended or inactive Locobuzz agents are migrated as inactive HubSpot users to preserve historical assignment records. The customer decides whether to keep inactive agents as system users or archive them.

Locobuzz SLA rules define response and resolution time windows per priority level and channel. We export SLA rules as structured metadata (SLA name, priority, response_time_hours, resolution_time_hours, reminder_trigger). HubSpot Professional and Enterprise tiers support SLA monitoring natively. We re-create SLA configurations in HubSpot's SLA settings using the exported rule parameters. SLA rules are not migrated as code; they require manual rebuild in HubSpot's SLA configuration UI post-migration.

Locobuzz tag taxonomy (applied across tickets, customers, companies, and reviews) migrates to HubSpot's native Tag system. Tags are preserved as labels on the corresponding HubSpot object at import time. If a tag maps to a routing or escalation logic in Locobuzz, we document that association in the workflow inventory for the customer's admin to rebuild in HubSpot as a Workflow trigger.

Locobuzz Social Account configurations (linked social profiles, channel types, account-level routing preferences) are workspace-level settings. We export the list of connected accounts and their routing preferences as a written configuration document. Social account re-connection is a manual step in HubSpot's settings because HubSpot uses its own social inbox and messaging integrations rather than Locobuzz's social channel connector setup.

Locobuzz AgentIQ sentiment scores and urgency flags are stored in a separate AI layer from the raw ticket record. We export both the structured ticket fields and the AI enrichment payload where accessible. If the AI layer export is not available, we flag it before migration so the customer knows sentiment history may not carry forward. Where accessible, sentiment and urgency scores migrate as custom number fields on the HubSpot Ticket record.

ResponseGenie suggested-reply data is part of the Locobuzz AI layer. We export suggested reply history where accessible as text fields on the corresponding HubSpot Ticket records. ResponseGenie does not have a functional equivalent in HubSpot Service Hub; Breeze AI at Enterprise tier provides agent assist features but does not replicate the ResponseGenie model directly. We document the availability of Breeze Customer Agent as the closest HubSpot equivalent.

Locobuzz analytics dashboards are platform-native visualizations built on aggregated ticket data. These cannot be exported as functional reports. We export underlying data (ticket volumes by channel, resolution times, CSAT scores where present, agent workload metrics) as CSV files for the customer to rebuild in HubSpot's reporting dashboard. HubSpot Professional includes custom report types; Enterprise includes advanced reporting with Breeze AI. The rebuilt report structure is outside migration scope and handled by the customer's admin or a HubSpot partner.