Migrate from Spotler CRM to HubSpot

Spotler contacts map directly to HubSpot contacts. HubSpot's lifecycle stage property (lifecycle_stage) is set based on Spotler's contact status value — we map each Spotler status pick-list value to the nearest HubSpot lifecycle stage and flag unmapped values before migration runs.

Spotler organizations map to HubSpot companies. Parent-child organization hierarchies in Spotler preserve via HubSpot's 'parent company' association. Multi-contact organizations collapse to one primary company with all contact associations preserved in HubSpot's company-contact relationship model. If an organization has multiple branch offices represented as separate records, each branch is linked to the parent company in HubSpot, ensuring a clean hierarchical view for reporting.

Spotler deals map to HubSpot deals. Each Spotler pipeline maps to a separate HubSpot pipeline with its own stage set. Stage names require value-by-value mapping — we extract Spotler's stage names and create corresponding HubSpot pipeline stages, preserving stage order and probability weights as custom fields.

Spotler's built-in quotations (line items + PDF generation) transform to HubSpot deal line items. The quotation header fields map to deal properties; line items map to HubSpot line item objects associated with the deal. PDF generation requires HubSpot Sales Hub Professional or higher — flagged before migration.

Spotler cases map to HubSpot tickets. Case status (open, pending, resolved) maps to HubSpot ticket status (open, closed). Case priority maps to HubSpot ticket priority (low, medium, high, urgent). Case owner resolves by email match against HubSpot owners. When multiple cases share the same subject, they are linked via HubSpot's association API to keep related tickets grouped for efficient support handling.

Spotler logged calls map to HubSpot call engagements with original call date, duration, and outcome preserved. Call notes migrate as engagement metadata. Owner resolves by email match — unmatched owners attach to a migration service account for review. If a call was logged under a deleted Spotler user, the engagement is assigned to a designated migration placeholder, and the original owner email is stored in a custom property for reference.

Spotler logged emails (via MailSync or manual log) map to HubSpot email engagements. Subject, body preview, and timestamp preserved. HubSpot's email tracking flag (email_open, email_click) is set based on Spotler's tracking data where available. For emails without tracking info, we set the engagement source to 'imported' so your team can differentiate migrated records from new inbound messages.

Spotler meetings map to HubSpot meeting engagements with original start/end times, location, and title preserved. Attendee list maps to contact associations on the meeting engagement. If a meeting includes external participants without existing HubSpot contacts, we create placeholder contacts linked to the meeting so you can follow up later.

Spotler notes map to HubSpot notes. Rich-text formatting in Spotler notes is preserved as HTML content in HubSpot notes. Notes attached to specific contacts or deals link via HubSpot's association model. Any embedded images or file attachments within notes are re-uploaded to HubSpot Files and linked back to the note for complete reference.

Spotler document attachments on contacts, organizations, and deals re-upload to HubSpot Files. File associations link to the parent record in HubSpot. File size limits apply (HubSpot caps at 25MB per file) — files over limit are flagged for chunking or alternative delivery.

Spotler users resolve to HubSpot owners by email match. Unmatched Spotler users are flagged before migration — your team either invites them to HubSpot or reassigns records to an existing owner. Archived/inactive Spotler users attach to a migration service account.

Spotler custom fields map to HubSpot custom properties. Property type is preserved (text → string, number → number, date → date, pick-list → enumeration). Multi-select pick-lists in Spotler map to HubSpot multi-checkbox properties. Custom field labels and help text are preserved for rebuild reference.

Spotler automations (triggers, conditions, actions) do not migrate. We export your Spotler automation definitions as a structured document — trigger types, conditions, and action sequences — for your HubSpot admin to rebuild as HubSpot workflows. The export is delivered alongside the migration plan.

Spotler custom reports and dashboards do not migrate. The underlying data (contacts, deals, activities) is in HubSpot, but report configurations and chart layouts must be rebuilt. We flag which HubSpot native reports cover the same metrics as your Spotler reports.