Migrate from Genoo to Pipedrive

Genoo Leads map to Pipedrive People. We use the email address as the dedupe key during import. Pipedrive's People object supports both Lead-style records and Contact-style records; we import all Genoo Leads as People with a 'Lead' label so that the customer's team can manually convert to Contact status if needed. Custom fields on Genoo Leads map to Pipedrive custom fields of matching type. We preserve the original Genoo Lead ID in a custom field genoo_lead_id__c for audit trail and any future cross-reference.

Genoo Contacts (populated through landing page captures and imported lists) map to Pipedrive People alongside Leads. We deduplicate by email address, merging records if the same email appears in both Genoo Lead and Contact exports. Name, email, phone, and any custom contact properties migrate to Pipedrive Person fields. The landing page source (which page submitted the form) maps to a custom field landing_page_source__c if that data is present in the Genoo export.

Genoo Account records (company name, website, industry) map to Pipedrive Organization. Genoo's Account data is sparse compared to Pipedrive's Organization schema, which supports additional fields. We import available fields and leave remaining Pipedrive Organization fields blank for the customer's team to populate post-migration. Organization is created before Person import so that the Organization link is resolved at Person insert time.

Genoo Campaigns (drip programs and email nurture sequences) map to Pipedrive Activities labeled with a 'Campaign' category. Campaign name, status, start/end dates, and program step descriptions migrate as Activity details. Campaign membership (which Leads entered which Campaign) migrates as Activity records linked to the corresponding Person, with the Activity subject indicating the Campaign name and the body describing the program step.

Genoo Campaign membership records (the association of a Lead to a Campaign) map to Pipedrive Activity records. Each membership becomes an Activity linked to the Person, with the Activity type set to 'Campaign enrollment' and the title or subject referencing the Campaign name. The sequence step or enrollment date migrates as the Activity date and description. Multiple memberships for a single Person create multiple Activity records in the Person's timeline.

Genoo Opportunities are not native records; they are CRM-synced entries that derive from the connected destination CRM. If the customer used Salesforce CRM sync, we attempt to extract Opportunity associations from Genoo's export if available, and map them to Pipedrive Deals. Deal name, value, and stage map from the source association. If no Opportunity export exists, we document this gap and recommend the customer extract Opportunity data directly from their CRM before migration.

Genoo form submissions and landing page captures (webinar registrations, content downloads, contact requests) map to Pipedrive Activity records with type 'Form submission.' The Activity subject captures the form name, the body captures field values where relevant, and the Activity date captures the submission timestamp. Form submissions without a matching Person email are held in a reconciliation queue for the customer to resolve.

Event registrations in Genoo (event name, date, registration status, attendance status) map to Pipedrive Activity records with type 'Event.' The Activity subject is the event name, the date is the registration or event date, and the body contains registration status and attendance data. Post-event attendance records (if exported) migrate as a follow-up Activity note.

Genoo lead scores are calculated values from the platform's scoring engine and are not included in any export format. We do not migrate lead scores. During discovery, we document the Genoo scoring configuration (demographic weights, behavioral thresholds, active rules) and advise the customer to configure Pipedrive's native lead scoring or a third-party scoring tool using the documented Genoo model as a reference. Lead scoring rebuild is out of migration scope.

Genoo's content library stores images, PDFs, and campaign files with no bulk file download API. We do not migrate binary assets. We generate a manifest of referenced content library URLs during discovery and instruct the customer to download files manually from the Genoo UI before account closure. Referenced image URLs in email templates are documented as broken-image risk if assets are not pre-downloaded.

If the customer's Genoo instance used Zapier workflows to push data to a CRM or other destination, we document the active Zapier zap configurations during discovery as a written inventory. Pipedrive's own Automation feature or Zapier rebuild is out of migration scope. We flag which Zapier zaps should be disabled during migration to prevent duplicate record creation during the data load.