Migrate from Genoo to HubSpot

Genoo stores all contacts in a single lead database with score, lifecycle stage, and campaign association. These map directly to HubSpot Contacts. The Genoo lead score becomes a custom property (Lead_Score__c) since HubSpot has no native equivalent. Original create dates are preserved as a custom datetime field since HubSpot's Createdate is set at migration time.

Genoo company records map 1:1 to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot standard properties. Parent-child company relationships in Genoo map to HubSpot's parent company association. Additional fields such as address, phone number, and any Genoo custom properties also transfer, preserving data types. When Genoo industry values differ from HubSpot's defaults, a value mapping step normalizes the data during import.

Genoo deal data synced from a CRM via Zapier migrates as HubSpot Deals. Deal name, amount, stage, and close date map to HubSpot deal properties. Each Genoo deal pipeline becomes a HubSpot deal pipeline. Deals without a primary company are flagged for manual assignment in HubSpot.

Genoo deal pipelines map to HubSpot deal pipelines. Pipeline stages in Genoo map to HubSpot deal stages per pipeline. Stage order and probability are preserved. HubSpot allows multiple pipelines with different stage sets — each Genoo pipeline gets its own HubSpot pipeline.

Genoo campaign records do not have a direct HubSpot equivalent at the CRM level. Email open, click, and unsubscribe events from Genoo campaigns are migrated as engagement activities on the relevant HubSpot contacts, preserving the campaign context as a note or activity property.

Genoo's native lead scoring — with demographic and behavioral weights — has no HubSpot CRM-native equivalent. We migrate the calculated score as a custom numeric property on each HubSpot contact. You can use this score in HubSpot workflows or list filters immediately after migration.

Genoo lifecycle stages (subscriber, lead, MQL, SQL, customer) map to HubSpot's lifecycle_stage property using the same values. This preserves segmentation built in Genoo and ensures HubSpot workflows triggered by lifecycle stage changes operate correctly from day one. Any custom stage labels that do not match HubSpot's standard set are mapped to the closest equivalent, with a note in the field mapping document for your team to review.

Genoo landing pages and microsites are website assets and do not migrate. Form submissions and the contact data captured by those forms are extracted and merged into the appropriate HubSpot contact records. Pages must be rebuilt in HubSpot CMS or your existing web platform.

Genoo automation rules, drip sequences, and behavioral triggers do not migrate to HubSpot. We export a machine-readable definition of each workflow so your HubSpot admin can rebuild the logic in HubSpot's workflow builder. This export includes trigger conditions, time delays, and email content references.

Genoo file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. File size limits apply (HubSpot's 25MB per file). Inline images in Genoo notes are extracted and rehosted in HubSpot's file manager. Files exceeding HubSpot's 25MB limit are stored as URL references in the record and remain accessible via the original source. Metadata including upload date and owner is preserved during transfer.

Any Genoo custom fields not mapped to HubSpot standard properties are migrated as HubSpot custom properties. Custom property types (text, number, date, picklist, checkbox) are preserved. Custom property names in Genoo map to HubSpot's internal property name format (snake_case or camelCase depending on creation method).

Genoo tasks and notes migrate to HubSpot engagements. Call logs, email body content, meeting records, and note text are mapped to the corresponding HubSpot engagement type with original timestamps and owner assignments preserved. Attachments linked to a task or note are transferred to HubSpot's file manager and attached to the engagement record. Custom task statuses map to HubSpot engagement statuses or become custom properties for review.