Migrate from Constructor to Pipedrive

Constructor CRM contacts map 1:1 to Pipedrive persons. The name, email, phone, and address fields carry over directly. The primary company link becomes the org_id field on the person record. Multi-company contacts in Constructor CRM map to a single primary org_id with additional organization associations noted in a custom field.

Constructor CRM companies map to Pipedrive organizations. Name, domain, industry, and employee count fields translate to Pipedrive's organization name, address, and custom fields. Parent-company hierarchies map using Pipedrive's parent_org_id field where supported by the data model. Address components from Constructor CRM (street, city, state, postal code, country) split into Pipedrive's structured address fields to enable location-based filtering and mapping features.

Constructor CRM deals map to Pipedrive deals with the deal name, value, expected close date, and owner carrying over. The deal's current stage in Constructor CRM maps to a specific stage within the designated Pipedrive pipeline. Each Constructor CRM pipeline becomes a separate Pipedrive pipeline.

Constructor CRM pipelines map 1:1 to Pipedrive pipelines. The pipeline name and stage count are preserved. Pipedrive requires that each pipeline is created before deals can be assigned to it — we create pipelines first during schema setup and then assign deal stage mappings per pipeline.

Constructor CRM stage names map to Pipedrive stage names within each pipeline. Stage probability values map as pipeliner probability on each stage. Stage sequence order is preserved. Stages with no equivalent in Pipedrive are noted for manual review before migration.

Constructor CRM call logs with duration, outcome, and notes map to Pipedrive activities with type=call. The call outcome (completed, no answer, voicemail) maps to Pipedrive's sub-type field where available. Original call timestamp and owner are preserved on the activity record.

Constructor CRM email records with subject, body preview, and timestamp map to Pipedrive email activities. Full email body content is preserved where the API returns it. Email attachments are downloaded and re-uploaded to Pipedrive's file attachment on the associated deal or person.

Constructor CRM meetings with title, start time, end time, and attendees map to Pipedrive meeting activities. The original meeting duration and location details are preserved in the activity notes field. Associated attendees map to person links on the Pipedrive activity.

Constructor CRM notes with content and author map to Pipedrive notes. Notes are linked to the associated person, organization, or deal record. Rich-text formatting in Constructor CRM notes is preserved as plain text with line breaks in Pipedrive's note field.

Constructor CRM custom fields on contacts require pre-creation in Pipedrive via POST /personFields. Each custom field gets a hash-based key that must be referenced in the import. We generate the field creation plan with exact field types (text, numeric, date, dropdown) and key assignments before data migration begins.

Constructor CRM deal custom fields map to Pipedrive deal custom fields. Pipeline-specific custom fields in Pipedrive require each pipeline to have the field explicitly enabled — we handle pipeline field scoping in the Pipedrive setup phase. Dropdown-type custom fields require value-by-value mapping if the source values differ from Pipedrive options.

File attachments on Constructor CRM records are downloaded and uploaded to Pipedrive's file storage associated with the matching record. File size limits apply (Pipedrive's default upload limit is 50MB per file). Inline images in notes are extracted and rehosted as attachments on the note or parent record.

Constructor CRM owner IDs are resolved by matching the owner's email address to a Pipedrive user. Users who do not exist in Pipedrive are flagged before migration — the team either creates the Pipedrive user first or assigns records to a designated fallback user. Active and inactive Constructor CRM users are handled separately.

Constructor CRM workflow rules with triggers, conditions, and actions do not migrate to Pipedrive. Pipedrive automations use a different trigger-action model. We export Constructor CRM workflow definitions as a reference document for rebuilding in Pipedrive's Automation builder. Sequences (email cadences) are also not migrated and must be set up in Pipedrive's Sequences feature.