Migrate from Genoo to Freshsales

Genoo Leads map directly to Freshsales Leads. We extract all standard lead fields (first name, last name, email, phone, company, website, source) from Genoo's manual export and import via Freshsales CSV import wizard or API. Any custom lead properties present in the Genoo export get mapped to corresponding Freshsales custom fields, which we create during schema preparation. The email address serves as the unique identifier for deduplication.

Genoo Contacts from landing page captures and imported lists map to Freshsales Contacts. We preserve Contact name, email, phone, and any custom properties. Where the destination uses a unified Contact model, we preserve the source as a custom field g_source__c to indicate original capture method. Freshsales' Contact object includes additional fields (Job Title, Address, Timezone) not natively present in Genoo, which we populate where data exists or leave blank for manual enrichment.

Genoo links Leads and Contacts to Account records with limited fields (company name, website, industry). We map Accounts to Freshsales Account, preserving the company name as the Account Name and the website as the Website field. Industry maps to the Freshsales Industry picklist. Any additional account-level data in Genoo migrates to custom Account fields we create before import. Account records must be imported before Contacts to satisfy the Freshsales Account-Contact lookup relationship.

Genoo Campaigns represent drip programs and email nurture sequences. We map Campaign records including name, status, start/end dates, and associated program steps to Freshsales Campaign. Campaign membership (which Leads entered which Campaign) migrates as a lookup table linked by email address to the corresponding Freshsales Contact or Lead record. Post-migration, Campaign membership enables Freshsales reporting on marketing-sourced leads and Campaign ROI.

Genoo stores which Leads enrolled in which Campaigns as an association table. Freshsales has no Campaign Member object equivalent, so we resolve Campaign membership as custom Contact fields or tags (campaign_name__c, campaign_enrollment_date__c) for active programs. For reporting purposes, we create Freshsales Campaigns and attach Contacts via Campaign Member records using the Freshsales CRM migration path where available, or via CSV import with Campaign ID resolved at migration time. This preserves marketing attribution history without duplicating records.

Genoo landing pages and microsites store form submissions as structured data (field label, field value, submission timestamp). We extract the form submission data and either create a Freshsales custom object (Landing_Page_Submissions__c) with lookup to Contact, or map the form fields to custom Contact fields if the form is simple. The page content itself (HTML) is flagged as a blob and documented for the customer's marketing team to rebuild in Freshsales Forms or a CMS.

Genoo email templates are HTML-based with subject line and body content. We extract template name, subject line, and HTML body from Genoo exports. Modern email builders in Freshsales use drag-and-drop blocks that do not map cleanly to raw HTML, so we preserve the template body as a reference document and note that the customer's admin rebuilds templates using Freshsales' visual email builder. Subject lines and preheader text migrate as text fields for reuse.

Event registrations in Genoo are stored as Activity-type records linked to Leads. We import registration data (event name, registration date, registration status) as Freshsales Activity records (Tasks or Events) linked to the corresponding Contact. Post-event attendance and survey data present additional challenges because Genoo does not reliably export this data separately; we flag attendance history as a gap in the migration report and recommend Freshsales event management as the rebuild path.