Migrate your Unanet CRM by Cosential data

Companies map cleanly to standard Account objects. We preserve all standard fields and company associations. Company type (Architect, Engineer, Contractor, Owner) is stored as a picklist value that we map directly.

Contacts are standard objects with name, email, phone, and role fields. We handle the Group Contact concept as a linked association rather than a separate object type. Contact-to-company relationships are preserved via the Company Association object.

Unanet's Company Association object links Contacts to Companies with a specific relationship role (e.g., Primary Contact, Project Manager, Estimator). We preserve these as a junction table but remap role values to the destination CRM's equivalent terminology.

Pursuits are Unanet's pipeline object for AEC project-based opportunities. They include pursuit stage, probability, estimated value, and pursuit history. We map pursuit stages to destination pipeline stages and preserve the stage-history timestamp trail as a custom activity log.

Project records include project name, status, client, contract value, and project manager. We migrate Projects as standard Opportunity objects with project-specific fields preserved. Active vs. completed status is preserved as a lifecycle field.

Group Contacts allow a single contact to belong to multiple company groups or roles within an AEC firm. We decompose these into Contact records with multiple Company Association rows rather than a separate object in most destination systems.

Qualification records track firm-level certifications, specialties, and past performance. These are stored as custom objects in Unanet. We map them to the destination's custom fields or a custom object and flag any that require custom field creation in the target.

Proposal templates, project profiles, resumes, and government forms are stored as attachment-linked objects. We migrate attachments as document records and flag which ones are tied to a specific Company, Contact, or Pursuit for relationship preservation.

Unanet allows extensive custom fields per object. We enumerate all custom fields during discovery, classify them by data type, and map them to destination custom fields. Any fields without a destination equivalent are flagged for customer review before import.

Documents linked to Companies, Contacts, Pursuits, or Projects are migrated as file records with parent reference preserved. We handle PDF, DOCX, and image formats. File size limits are checked against the destination system during scoping.

Calls, emails, meetings, and notes are stored as interaction records tied to any parent object. We migrate these in chronological order and preserve the linked entity reference. Note content is migrated as plain text with HTML stripped if the destination is plain-text only.