Migrate from Skyward CRM to Pipedrive

Skyward CRM Contact records map to Pipedrive Person objects. Standard fields (name, email, phone, address) migrate directly. We use email as the deduplication key. Skyward Contact owner assignments map to Pipedrive OwnerId via email matching against the destination User roster. Any Skyward Contact without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to provision first.

Skyward CRM Lead records migrate to Pipedrive Lead. Lifecycle stage data (unqualified vs qualified) transfers to a custom field in Pipedrive to preserve segmentation. Lead status values from Skyward map to Pipedrive's Lead Status picklist. We extract leads separately from contacts to preserve the prospect lifecycle before conversion.

Skyward CRM Company records map to Pipedrive Organization. We extract company records first in the migration sequence to establish foreign-key relationships before importing child Person records. The company domain becomes the Organization's Website field. Organization is created before any Person import so that the OrgId lookup is satisfied at the moment of Person insert.

Skyward CRM Deal records map to Pipedrive Deal. Each Skyward deal pipeline becomes a Pipedrive pipeline with custom stages. Deal owner, deal value, currency, expected close date, and associated Person and Organization links migrate directly. We resolve the PersonId and OrgId references at migration time using the email-to-Person and domain-to-Organization lookup.

Skyward CRM allows fully customizable pipeline stage names with no standardized values. We capture the complete pipeline configuration during scoping and produce an explicit stage-mapping table for each pipeline. Multi-stage pipelines with conditional transitions require additional validation to confirm all Deal records land in the correct stage after import. Pipedrive stages are defined per pipeline and must be created before Deal import.

Skyward CRM Activity records (calls, emails, meetings, tasks) tied to Contacts and Deals migrate to Pipedrive Activity objects. We preserve activity type, date, duration, and notes. Activity timestamps normalize to UTC during import. Complex activity threads with multiple participants link to the correct Person or Deal via the WhatId reference. Skyward's activity type taxonomy maps to Pipedrive ActivityType values.

Skyward CRM Product catalog entries linked to Deals migrate to Pipedrive Products. We extract product records including name, SKU, pricing, and description. Product-to-Deal associations require junction-table handling during import to preserve the many-to-many relationship. Pipedrive Products must exist before Deal-product associations can be created.

Skyward CRM sales team members assigned as record owners migrate to Pipedrive User records. We extract the full user roster and map owner assignments via email match. Any Skyward Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Skyward owners map to inactive Pipedrive users to preserve historical assignment.

Skyward CRM supports custom fields on core objects but does not expose a public metadata API. We discover custom fields during scoping by accessing the Skyward CRM admin panel and enumerating fields per object. Each discovered custom field gets a corresponding custom field in Pipedrive with type mapping (text to string, date to date, picklist to picklist). Pipedrive custom fields are created during import via the mapping step. Any missed custom field results in a post-migration data gap review.

Skyward CRM's partner management module stores partner entities with a distinct schema including partner type, commission structure, and shared lead attribution. Partner records do not automatically merge with contacts even when the partner is also a customer. We extract partners into a separate staging table and map them to Pipedrive Organization (for partner companies) or Person (for individual partners) based on the partner type. Commission structure and lead-sharing fields map to custom Pipedrive fields. The customer chooses the mapping strategy during scoping.

Reports in Skyward CRM are generated from live data and are not stored as independent record sets. We do not migrate reports because they are configuration artifacts rather than data. Customers rebuild reports in Pipedrive's reporting module post-migration. We deliver a written inventory of every Skyward CRM report with its filter criteria and visualization type as a rebuild reference.