Migrate from Patent Hive to Pipedrive

Hive projects map directly to Pipedrive Organizations. The project name becomes the organization name, and the project description, creation timestamp, and any custom properties are transferred to custom fields on the Organization for audit continuity. We optionally add a custom pick‑list field (Source_Project__c) on the Organization so Pipedrive users can filter by the original Hive project, preserving full project context and enabling historical reporting in Pipedrive.

Hive workspace members map to Pipedrive users by email match. The mapping uses the email address as the unique identifier; any Hive member without a corresponding Pipedrive user is recorded in a pre‑migration report, allowing your team to decide whether to invite them or use a designated fallback owner. This ensures all task assignments remain traceable after migration.

Hive tasks translate to Pipedrive Activities (type=task). The task name becomes the activity subject. Original due date, assignee, creator, priority, and status are preserved as custom fields on the activity or as linked field values. Note that Pipedrive activities do not have a native Kanban view.

Hive labels (e.g., 'Sales Follow-up', 'Contract Review') have no Pipedrive native equivalent. We create a multi-select or single-select custom field on Pipedrive Activities to preserve the label set. The migration plan includes the full label inventory from Hive for your Pipedrive admin to pre-create the field options.

Hive project-level custom properties (e.g., 'Project Type', 'Department', 'Contract Value') migrate as Pipedrive custom fields on the Organization object. Field type is matched by Hive's property type — text, number, date, or pick-list. Before migration, your Pipedrive admin creates these fields, and FlitStack maps the field names to Pipedrive's 40‑character hash key format. The values are then transferred during the migration run, preserving the original data for reporting in Pipedrive.

Hive task-level custom properties migrate as custom fields on Pipedrive Activities. The same Hive property that appears across many tasks becomes one Pipedrive custom field definition used across all activity records. Before migration, your Pipedrive admin creates these custom fields, and FlitStack maps each to Pipedrive's 40‑character hash key format. The values are then transferred during the migration run, preserving the original data in Pipedrive Activities.

The Hive user assigned to a task maps to the Pipedrive user who owns the resulting Activity. Resolution is by email match. If no Pipedrive user matches the Hive assignee email, the activity is assigned to the migration fallback owner and flagged for review.

Hive's project-contains-tasks structure translates to Pipedrive: the Hive Project becomes a Pipedrive Organization, and each Hive Task becomes a Pipedrive Activity linked to that Organization. The org_id is resolved during migration so the relationship is explicit in Pipedrive's activity detail view.

Hive file attachments on tasks are downloaded and re‑uploaded to the corresponding Pipedrive Activity via the Pipedrive Files API. FlitStack preserves the original file name and uploads it to the linked Activity; if a file exceeds the size limit of your Pipedrive plan, the system flags it for manual review, allowing you to split the file or adjust your storage plan before finalizing the migration.

Hive automations (due-date triggers, assignment rules, notification rules) do not have Pipedrive equivalents because Pipedrive's automation engine uses deal-stage and CRM-field triggers rather than project-task triggers. We export Hive workflow definitions as a structured reference document for your Pipedrive admin to rebuild from.