Migrate from Salesflo Engage to HubSpot

Salesflo Engage contacts map directly to HubSpot contacts. Email, phone, name, job title, and address fields transfer 1:1. HubSpot contact model supports the association to a primary company, which is resolved from Salesflo Engage contact-company link. This direct mapping ensures that all contact information is preserved and accessible within HubSpot contact management system.

Salesflo Engage company or retailer records become HubSpot companies. Company name, domain, industry, city, state, country, and employee count transfer directly. Each unique location in Salesflo Engage must exist as a separate HubSpot company to support visit-location associations. This separation ensures that visit-location data is accurately represented in HubSpot company management.

Salesflo Engage visits have no native HubSpot equivalent. Each visit becomes a HubSpot deal with custom fields for visit type (planned vs. unplanned), visit status, check-in time, check-out time, GPS latitude, GPS longitude, and store name. Original create date and owner are preserved. Visit-location associations are resolved via company links on the deal.

Salesflo Engage supports multiple locations per visit. HubSpot model requires a different approach: each location is a separate Company record, linked to the deal via HubSpot native association. If a visit spans multiple locations, FlitStack creates multiple deal records with a shared custom reference ID to preserve the original grouping.

Salesflo Engage tasks map directly to HubSpot tasks. Subject, due date, priority, status, and owner transfer. HubSpot tasks appear in the contact and company timeline, maintaining the activity context from the source. This ensures that all task-related information is preserved and visible within HubSpot activity tracking features.

Form name and field answers from Salesflo Engage become custom properties on the relevant HubSpot record (contact for field rep surveys, deal for store audits). Submission timestamp is preserved as a custom datetime property. HubSpot custom properties are created before migration begins.

Salesflo Engage team members are resolved to HubSpot users by email address. Role or designation migrates as a custom property on the user record for reference. If a team member has no matching HubSpot user, the record is assigned to a designated fallback owner and flagged for review.

Salesflo Engage call, email, and meeting records migrate as HubSpot engagement timeline events. Subject, outcome, duration, notes, timestamps, and owner transfer. Each activity is associated to the correct contact or deal record in HubSpot. This migration preserves the full engagement history and ensures that all communication records are accessible within HubSpot timeline view.

Salesflo Engage custom objects map to HubSpot custom objects (requires HubSpot Enterprise tier). We create the custom object definitions in HubSpot first, then migrate all records with their field data. Associations between custom objects and standard objects become HubSpot native associations.

Files attached to visits, tasks, or form submissions in Salesflo Engage are re-uploaded to HubSpot as file attachments on the relevant record. File size limits per HubSpot apply. Inline images in notes are extracted and rehosted as HubSpot-hosted files. This ensures that all attachments are preserved and accessible within HubSpot file management system.