Migrate from Genoo to Salesforce Sales Cloud

Genoo Leads map directly to Salesforce Lead. Standard fields (FirstName, LastName, Email, Phone, Company, LeadSource) migrate from Genoo's Lead export file. Genoo's lead status values map to Salesforce Lead Status picklist values, and the source campaign attribution is preserved by linking the Lead to a Salesforce Campaign via a Campaign ID custom field. We validate email format and remove records with missing required fields before insertion.

Genoo Contacts from landing page captures and imported lists map to Salesforce Contact. We extract name, email, phone, and any custom properties from the Contact export file. Since Genoo does not enforce a Lead-to-Contact conversion model, we treat all Genoo Contacts as Salesforce Contacts directly. If a Contact in Genoo shares an email with a Lead record we are also migrating, we deduplicate by preferring the more recently updated record and flagging the duplicate for admin review.

Genoo Account records map to Salesforce Account. The Account object in Genoo stores limited fields: company name, website, and industry. We use the company name as a deduplication key during import. Where the same company appears across multiple Contact records in Genoo, we create one Salesforce Account and link all Contacts to it. We derive the Account industry from Genoo's industry field where populated and leave it blank where absent.

Opportunities are not a native first-class object in Genoo; they are derived from the CRM sync side where the destination CRM owns the Opportunity. We import the opportunity association data captured in Genoo's sync export — opportunity name, stage, amount, close date, and linked contact or account — as Salesforce Opportunity records with a custom sync_source__c field set to Genoo. If no opportunity data exists in Genoo (because the team relied on Salesforce directly), we note the Opportunity association as a post-migration admin task.

Genoo Campaigns (drip programs and email nurture sequences) map to Salesforce Campaign. We import Campaign name, status, start and end dates, type, and associated program steps. Campaign membership — which Leads enrolled, when they enrolled, and their completion status — migrates as Salesforce CampaignMember records linked to the corresponding Salesforce Campaign. Engagement metrics such as opens and clicks from Genoo are not stored as structured data in the export and are not migratable; we document this gap for the customer's analytics team.

Event registrations in Genoo are stored as Activity-type records linked to Leads. We import registration data — event name, event date, registration status, and any registration notes — as Salesforce Task records with a custom field event_type__c set to Registration. Post-event attendance and session data from Genoo's event module do not have a direct Salesforce equivalent and are not migrated; we document the event configuration separately for the customer's admin to rebuild as Salesforce Events or a connected event platform.

Genoo landing pages and microsites are stored as HTML or template blobs with associated form field configurations. We extract page content, form field names, and thank-you page redirect URLs as structured data. The full rendering assets do not map to any standard Salesforce object. We preserve HTML content in a custom Long Text Area field on the related Salesforce Campaign record for manual review. Forms embedded within landing pages are documented for Salesforce Web-to-Lead configuration rebuild.

Genoo email templates are HTML-based. We extract the template body, subject line, and inline CSS styling from the export. Drag-and-drop visual builder blocks used in Genoo templates do not export as clean HTML and cannot be reconstructed automatically. We extract what is available as structured fields and flag the visual block components that require manual rebuild in Salesforce Lightning Email Template builder or a third-party email design tool.

Genoo workflow configurations and automation rules are stored as internal database entries rather than structured exportable records. We do not migrate automation configurations as code because no equivalent automation model exists in Salesforce Sales Cloud and the configurations cannot be extracted from Genoo's platform. We document every active workflow, trigger, condition, and action during the discovery phase and deliver a written automation inventory with recommended Salesforce Flow equivalents for the customer's admin to rebuild post-migration.

Genoo calculates lead scores dynamically in its scoring engine and displays them in the UI. The calculated scores and the underlying scoring rules and weighting factors are not included in any Genoo export format. We do not migrate lead scores because the scoring model cannot be extracted. We document the scoring configuration during discovery and provide a written model description that the customer's Salesforce admin can use to configure Salesforce native lead scoring or Pardot scoring post-migration.

Genoo Owners referenced on Lead, Contact, and Campaign records are reconciled against Salesforce User records by email address match. Any Genoo Owner without a corresponding Salesforce User is held in a reconciliation queue for the customer's admin to provision before record migration begins. Owner mapping is validated before the Lead migration phase starts because OwnerId is a required field on most Salesforce standard objects.

Genoo's content library stores images, PDFs, and campaign files. The platform exposes no bulk file export API or download endpoint. We do not migrate binary assets automatically. We generate a manifest CSV listing every content library item with its URL and file type. The customer downloads files manually from Genoo's UI before the account is closed. We provide the manifest so the customer can re-upload assets to Salesforce Files, a connected CMS, or a cloud storage bucket post-migration.