Migrate from Maple CRM to HubSpot

Maple CRM leads map directly to HubSpot contacts. Email, phone, name, and address fields transfer as-is. The HubSpot lifecycle_stage property defaults to 'lead' for migrated records unless the source record indicates a later stage. Owner resolution matches Maple owner email to HubSpot user email.

Maple CRM customer records map to HubSpot contacts with lifecycle_stage set to 'customer'. All customer properties transfer to HubSpot contact properties, including custom fields. The Maple customer record ID is stored as Source_System_ID__c for traceability and future synchronization needs. Associated company links and deal associations are resolved using the same lookup mechanisms applied throughout the migration.

Maple CRM companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer directly. HubSpot's company record becomes the canonical record for all associated contacts. Multi-location companies in Maple CRM collapse to one HubSpot company with additional location properties.

Maple CRM deals map to HubSpot deals with the pipeline and stage values translated to HubSpot pipeline IDs and stage labels. Deal name, amount, close date, and owner transfer directly. Probability and forecast category are re-applied based on HubSpot's stage configuration after migration.

Maple CRM pipeline definitions become HubSpot deal pipelines. Each Maple pipeline creates a corresponding HubSpot pipeline, and Maple stage names map to HubSpot stage labels value-by-value. Stage probability values are set per stage in HubSpot's pipeline configuration, and forecast categories are assigned to match the sales motion semantics of the original pipeline.

HubSpot has no native contract object. Maple CRM contracts migrate as file attachments linked to the associated contact or company record. Contract metadata (expiry date, renewal terms, AMC type) transfers to custom properties on the contact or company for reference.

Maple CRM invoices and quotations have no direct HubSpot equivalent. PDF versions of invoices and quotes are migrated as files attached to the relevant deal or contact record. For Professional+ HubSpot accounts, quote line items can be created manually from the migrated data.

Maple CRM call logs, emails, and meeting records map to HubSpot engagements. Original timestamps, body content, and owner assignments are preserved. Call duration and outcome data transfer to HubSpot call properties. Meeting details including title, start/end time, and attendees map to HubSpot meeting records.

Maple CRM notes and uploaded documents attach to the corresponding HubSpot record. Text notes migrate as HubSpot notes with original create dates and author attribution preserved. File attachments re-upload to HubSpot Files, maintaining the association to the contact, company, or deal record throughout the migration process.

Maple CRM custom fields on leads and customers create HubSpot custom properties. Field types map to HubSpot property types: text fields, number fields, date fields, and pick-list fields each have corresponding HubSpot types. Pick-list values require value-by-value mapping when the source uses defined option sets.

If the Maple CRM setup includes service request tracking, these map to HubSpot Tickets. Ticket properties transfer to HubSpot ticket fields, and pipeline stages map to HubSpot ticket pipelines. Owner resolution applies the same email-match logic used for contacts and deals.

Maple CRM workflow rules and automation logic do not migrate. Triggers, conditions, and actions defined in Maple are exported as a structured reference document for rebuilding in HubSpot's workflow builder. The export includes conditional logic, action sequences, and time-based triggers so your team can recreate equivalent automations in HubSpot's automation framework.