Migrate from Insightly Marketing to HubSpot

Insightly Contacts map directly to HubSpot Contacts. The primary email address, phone, name fields, and address fields translate 1:1. Insightly's contact type distinction (Lead vs. Contact) routes based on the INSIGHTLY_LEAD field value into HubSpot's lifecycle_stage property — converted to 'lead' or 'customer' per the source record state.

Insightly's separate Lead object merges into HubSpot's single Contact object. All Lead fields — name, email, phone, company, status, source — map to the corresponding HubSpot Contact properties. The INSIGHTLY_LEAD flag is set to true on migrated records so the HubSpot lifecycle stage starts at 'lead' until manually progressed.

Insightly Organizations map to HubSpot Companies using direct field-to-property translation for name, domain, industry, employee count, annual revenue, and address fields. For industry fields where Insightly uses free-text entries, HubSpot's default country pick-list values are applied and free-text entries are mapped to 'Other' with the original value preserved in a custom property.

Insightly Opportunities map to HubSpot Deals. The opportunity name becomes the deal name, amount maps to amount, and close date maps to closedate. Pipeline and stage mapping requires a value-mapping step — each unique Insightly stage name maps to a corresponding HubSpot pipeline-stage value, creating a pipeline in HubSpot if one does not already exist.

Insightly stores opportunity-contact associations as separate link records with optional role labels. In HubSpot, the deal-to-contact relationship uses the associations API. Role labels that match HubSpot's built-in roles (decision-maker, influencer) map to those; other labels are stored as a custom contact property (opportunity_role) on the association.

Insightly Projects have no direct HubSpot equivalent. We create a HubSpot Custom Object named 'Project' and map standard fields (name, status, due date, description) to custom properties. Task records linked to the project become child records stored as a custom property (task_ids) with a JSON array of task summaries, or as a secondary custom object if your HubSpot plan supports it.

Insightly Tasks map to HubSpot engagements (calls, emails, meetings) or to Notes depending on the task category field. Task subject maps to the engagement subject; task status (completed/open) maps to the engagement timestamp; task due date becomes a HubSpot engagement property. Completed tasks with no outcome are stored as completed engagements for activity history continuity.

Insightly Notes map to HubSpot Notes. The note body (including HTML formatting) is preserved in HubSpot's note body. Original note author and create date are stored as custom properties on the note (note_author and note_original_date) since HubSpot's standard note timestamps reflect migration time.

Insightly email records (sent, received, logged) map to HubSpot email engagements. The email subject, body, sender, and recipient map to the corresponding HubSpot engagement fields. If the email was associated to a contact in Insightly, that association link is preserved via HubSpot's engagement-to-contact association endpoint.

Insightly custom objects map 1:1 to HubSpot custom objects. Each custom object in Insightly gets a corresponding HubSpot custom object with the same label. Custom object fields map to HubSpot custom properties, applying type-aware conversions (date strings to ISO 8601, currency to amount with currencyCode, pick-lists to HubSpot option sets).

Insightly's custom field groups — logical groupings of fields under expandable sections — map to HubSpot property groups on the destination object. The group name and field order are preserved. Fields that belong to a custom field group but are standard Insightly fields get their group assignment noted so the HubSpot admin can recreate the grouping.

Insightly file attachments (stored linked to contacts, organizations, opportunities) are downloaded and re-uploaded to HubSpot's file manager. File names and original URLs are preserved in HubSpot's file metadata. Inline images in notes are downloaded and re-hosted in HubSpot's file CDN so note rendering remains intact after migration.

Insightly owner IDs are resolved by email match against HubSpot users. Any Insightly owner without a corresponding HubSpot user is flagged during the pre-migration audit. Your team can either invite them to HubSpot first or reassign their records to a designated fallback owner before the migration commits.

Insightly tags on contacts and organizations map to a HubSpot custom multi-value property (tag_names) stored as comma-separated text. For tag-based segmentation, tags can alternatively be used to create HubSpot lists — each unique tag becomes a static list membership criterion.

Insightly workflow rules, sequence triggers, and automation conditions do not have a HubSpot equivalent at the data level. FlitStack exports your Insightly workflow definitions as a JSON specification file that your HubSpot admin can use as a reference to rebuild equivalent automations in HubSpot's workflow builder.