Migrate from Daffodil CRM to HubSpot

Daffodil CRM contacts map directly to HubSpot Contacts. Every contact property (name, email, phone, job title, address fields) maps to the corresponding HubSpot contact property. The contact's Daffodil CRM owner is resolved by email against HubSpot users and stored as the HubSpot owner. If Daffodil CRM stores a lifecycle status field, we map it to HubSpot lifecycle_stage as a custom property.

Daffodil CRM companies map to HubSpot Companies. Company name, domain/website, industry, employee count, and annual revenue map directly. Daffodil CRM parent-child company hierarchies map to HubSpot's Parent Company field. Multi-contact companies in Daffodil CRM attach all associated contacts via HubSpot's company association model.

Daffodil CRM deals map to HubSpot Deals with deal name, amount, close date, and owner transferred directly. The Daffodil CRM deal stage maps to the corresponding HubSpot pipeline stage by value. If Daffodil CRM supports multiple pipelines, we create equivalent HubSpot pipelines before migrating so each deal lands in the correct pipeline.

Daffodil CRM pipelines map to HubSpot Deal Pipelines. Each Daffodil CRM pipeline becomes a named HubSpot pipeline with its own stages. Stage order, stage names, and stage probabilities transfer. If Daffodil CRM uses a single default pipeline, we create a HubSpot pipeline with the same stage sequence. You choose the stage mapping before migration runs.

Daffodil CRM task records map to HubSpot Engagements. Call logs become HubSpot call engagements with subject, duration, and outcome. Emails logged in Daffodil CRM become HubSpot email engagements. Meetings become HubSpot meeting engagements with original start/end times and location preserved. Each engagement links to its parent contact or deal via HubSpot's association model.

Daffodil CRM notes map to HubSpot engagement notes. Note body text transfers; creation timestamp and note author (matched by email) are stored on the HubSpot engagement. Notes attach to the correct HubSpot record (Contact, Company, or Deal) via HubSpot's association API. Rich-text formatting in Daffodil CRM notes is preserved as plain text in HubSpot.

Daffodil CRM users are resolved to HubSpot Owners by email address. We query your HubSpot portal for existing users and match by email. Any Daffodil CRM owner without a corresponding HubSpot user is flagged in the pre-migration report — your team either creates the HubSpot user or assigns those records to a fallback owner. This prevents orphaned records.

Daffodil CRM custom fields on contacts become HubSpot custom contact properties. We create each custom property in your HubSpot portal (via Properties API) before the migration run, matching the field type (text, number, date, picklist). Picklist values map value-by-value. Multi-select fields in Daffodil CRM become multi-checkbox or multi-select properties in HubSpot.

Daffodil CRM custom fields on deals become HubSpot custom deal properties. We pre-create the property in HubSpot with the correct type before the migration batch runs. Deal-level custom fields that represent numeric scores or stage probabilities map to existing HubSpot deal properties where applicable.

Daffodil CRM file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Each file is attached to its parent CRM record via HubSpot's file associations. We preserve the original filename and file type. HubSpot's file size limit (25MB per file) applies; files exceeding this are flagged for manual handling.

Daffodil CRM products (if present) map to HubSpot Products with name, SKU, price, and description transferred. Products are migrated before deals so that deal line items can reference valid product IDs in HubSpot. If Daffodil CRM stores product inventory quantities, these become custom properties on HubSpot Products.

Daffodil CRM custom objects (if your account has them) map 1:1 to HubSpot Custom Objects. We create the HubSpot Custom Object schema first using the Schemas API, defining the display properties and associations. Custom object records migrate with all custom properties mapped. If Daffodil CRM uses N:N associations, we create HubSpot association types to preserve the relationship.