Migrate from Altcraft to Pipedrive

Discovery and Altcraft export feasibility assessment

We audit the Altcraft account to identify all Profile databases, custom field definitions, active Segments, Campaigns with linked Orders, active Automation Scenarios, and Communication Channel configurations. Because the Altcraft API is inaccessible (301 redirect), we assess whether CSV export is available from the UI, whether Albato integration credentials are accessible, or whether the customer can provide database-level access. We also count Profiles and flag any that lack email addresses, which prevents Pipedrive import without manual remediation. The discovery output is a written migration scope with the confirmed export path (CSV, Albato, or database) and a list of records that require data quality remediation before migration.

Data extraction and behavioral attribute extraction

We extract Profile data from Altcraft using the confirmed export path. For CSV exports, we flatten behavioral attributes (channel subscriptions, engagement scores, last-interaction dates, LTV estimates, Control Group membership) from the Profile's nested structure into flat columns that map directly to Pipedrive custom fields. We extract Campaign records with associated performance metrics, Product catalog data, and Order history with line items. For each export, we generate a record count and a sample of 50 rows for field mapping validation before committing to the full export.

Pipedrive account setup and custom field pre-creation

Before any data moves into Pipedrive, we create all required custom fields in the destination account. This includes custom fields for behavioral attributes (engagement_score__c, last_channel__c, last_interaction_date__c, lifetime_value__c, email_optin__c, sms_optin__c, push_optin__c, altcraft_profile_id__c, control_group__c), campaign metrics (open_rate__c, click_rate__c), and any Altcraft custom profile fields that lack direct Pipedrive equivalents. We also configure Deal stages to match the Altcraft campaign status and order status mapping. Pipedrive account configuration happens in parallel with data extraction to avoid delays during the migration window.

Organization and Person import in dependency order

We import Pipedrive Organizations first (derived from Altcraft Profile company fields), then Persons. The Organization import uses the Altcraft domain as a dedupe key to avoid duplicate Organizations. Person import uses email as the primary dedupe key and resolves the Organization link at insert time using the Organization name as the matching field. All custom fields for behavioral data are populated during the Person import. Any Altcraft Profiles without email addresses are exported to a separate remediation file for the customer to address manually before a second-pass import.

Deal, Product, and Order migration

We import Products first (since Deals reference Products via Deal-Product entries), then Deals with campaign metadata, then Order history restructured as Deals with linked Product entries. Each phase produces a reconciliation report showing record count, error count, and sample record validation before the next phase begins. Closed orders receive a won stage assignment; pending orders receive the appropriate pipeline stage from the configured status-to-stage mapping.

Scenario inventory and handoff package delivery

We deliver a structured Scenario inventory document listing every active Altcraft Automation Scenario with its trigger type, conditional branches, delay steps, action types, and referenced Profiles. For each Scenario, we propose an equivalent Pipedrive Workflow construct or note that no native equivalent exists and recommend a third-party automation tool. We also deliver a Channel Configuration handoff document, a Template content export (as structured text files), a Form and Survey structure export, and a Control Group mapping summary. We do not rebuild Scenarios, configure Pipedrive Workflows, or set up third-party automation tools inside the migration scope.

Cutover, validation, and billing offboarding

We confirm the Altcraft export is complete and no new records have been created since the last export window. The customer offboards Altcraft users and confirms the billing cycle end date to avoid profile-count charges extending beyond the migration. We perform a final reconciliation comparing Pipedrive record counts against the Altcraft export counts, verify Person-Organization links, verify Deal-Product links, and confirm custom field completeness on a 50-record sample. We do not provide post-migration admin support or training as standard scope; these are separate engagements.