Migrate from Unanet CRM by Cosential to Pipedrive

Unanet companies map directly to Pipedrive Organizations. Company name maps to organization name, domain maps to Web URL field, and industry classification maps to Pipedrive's industry pick-list. Parent/child firm hierarchies in Unanet collapse to a single Parent Organization link in Pipedrive.

Unanet contacts map to Pipedrive People. The primary contact for each company in Unanet becomes the linked Person in Pipedrive's Organization record. Additional contacts from Unanet's N:N company-contact associations migrate as additional Person records linked to the same Organization. All contact fields including name, email, phone, address, and job title transfer directly, while the Unanet owner assignment resolves via email match to a Pipedrive user.

Unanet pursuits are the core object to translate. Each pursuit maps to a Pipedrive Deal. The pursuit stage (Prospect, Pursuing, Shortlisted, Won, Lost) maps to Pipedrive deal stages configured per pipeline. Contract value and estimated value fields from Unanet translate to Pipedrive's weighted value and expected close date.

Unanet pursuit stage names require value-by-value mapping to Pipedrive pipeline stages. Prospect maps to the earliest open stage, Pursuing maps to middle evaluation stages, Shortlisted maps to a late-stage pre-decision column, and Won/Lost map to terminal closed-won and closed-lost stages in Pipedrive.

Unanet activity records — calls, emails, meetings, and notes — map directly to Pipedrive Activities. Activity type in Unanet translates to Pipedrive's activity_type field (call, email, meeting, task). Original timestamps, owners, and associated contact/pursuit links are preserved in the migration.

Unanet file attachments on companies, contacts, or pursuits re-upload to Pipedrive as file attachments on the corresponding Organization, Person, or Deal record. File size limits and inline image handling apply — images in rich-text notes are extracted and rehosted as separate attachments.

Unanet users are resolved by email address match against Pipedrive users. Unassigned records (owners in Unanet without Pipedrive accounts) are flagged before migration for your team to create accounts or reassign. Active user flag and last-login data are preserved for cleanup decisions.

Unanet tags on pursuits and contacts map to Pipedrive Labels. Tags used to categorize pursuit types, industry segments, or team assignments become Pipedrive labels for filtering and reporting. Duplicate tag values are deduplicated during ingest. Tag metadata including creation date and associated owner is preserved in a custom field where available, ensuring no categorization history is lost in the migration.

Unanet custom properties on pursuits — pursuit type, project classification, contract value range, AEC sector — create Pipedrive custom fields on Deals before migration. Field types are mapped: pick-list properties become Pipedrive enum fields, numeric properties become number fields, and text properties become text fields.

Unanet company-level custom properties such as bonding capacity, union status, and firm classification migrate as Pipedrive custom fields on Organizations. These require pre-creation in Pipedrive using the OrganizationFields API before data ingest begins. Field types are mapped: pick-list properties become Pipedrive enum fields, boolean properties become checkbox fields, and numeric properties become number fields, preserving all value options and defaults from Unanet.

Unanet proposal templates and proposal automation do not have a direct equivalent in Pipedrive. We export template definitions as a reference document for rebuilding in Pipedrive's Smart Documents feature (Professional+ tier) or a third-party proposal tool post-migration. Template data including company info, contact details, pursuit values, and branding assets transfer separately and are available for population into new templates without re-entry.

Unanet workflow automations tied to pursuit stage changes, assignment rules, and notification triggers do not migrate. We audit your current automations and produce a rebuild specification for Pipedrive's Workflow Automation feature, mapping each trigger and action to the equivalent Pipedrive automation configuration.