Migrate from Unanet CRM by Cosential to Salesforce Sales Cloud

Unananet Organization maps 1:1 to Salesforce Account. Organization name, industry, employee count, and annual revenue transfer as standard Account fields. Multiple Unanet locations on one organization collapse to the primary Account address; secondary locations require a Location__c custom object or Address records in Salesforce.

Unanet Individual maps directly to Salesforce Contact. First name, last name, email, phone, mobile, job title, and address fields transfer as standard Contact fields. Each Individual's primary Organization becomes the Contact.AccountId lookup. Original create timestamps are preserved as a custom Original_Create_Date__c field.

If your Unanet Individual records contain AEC-specific fields not represented in standard Salesforce Contact (e.g., Professional License Number, Certification Expiry Date), FlitStack creates a custom Individual__c object with __c fields and links it to the Contact via a lookup. All custom fields are enumerated during scoping.

Unanet Pursuit maps to Salesforce Opportunity. Pursuit name becomes Opportunity Name; pursuit amount becomes Amount; expected close date maps to CloseDate; owner email resolves to OwnerId. Pursuit stage maps to Opportunity StageName via a value-mapping table. Unanet's multi-pipeline-per-record model requires a custom Pursuit_Pipeline__c field when more than one pipeline is present.

Stage names in Unanet map value-by-value to Salesforce Opportunity StageName values. Stage probability, forecast category, and stage-entry timestamps are preserved as custom fields on Opportunity (Stage_Probability__c, Forecast_Category__c, Stage_Entered_Date__c). When multiple Unanet pursuit pipelines exist, we pre-coordinate with your Salesforce admin to create the correct RecordTypeId assignments before stage mapping runs.

Unanet pursuit team members — assigned individuals with a role on a pursuit — transfer as Salesforce OpportunityTeamMember records. Team member role maps to TeamMemberRole (e.g., Pursuer, Estimator, Subject Matter Expert). Primary contact flag maps to OpportunityContactRole with IsPrimary = true. Both objects require the parent OpportunityId to exist first, so team migration runs after opportunity insertion.

Unanet Proposal has no Salesforce native equivalent. FlitStack creates a Proposal__c custom object linked to the target Opportunity (via Proposal__c.Opportunity__c lookup) and the associated Account. Fields include: Proposal_Name__c, Amount__c, Status__c, Version__c, Created_Date__c, and Proposal_File_Reference__c (storing the original Unanet attachment URL or re-uploaded Salesforce Files link). Version history from Unanet is preserved as separate Proposal__c records keyed by version number.

Unanet stores past performance data (award value, client name, project description, contract type) as native pursuit fields. These map to a custom Past_Performance__c custom object with fields: Award_Value__c, Client_Name__c, Project_Description__c, Contract_Type__c, Start_Date__c, End_Date__c, and Contact__c lookup to the relevant Salesforce Contact. Linked to Opportunity via a lookup field for SF-1449 and past-performance reporting.

Unanet Project records (post-pursuit project tracking) transfer as a custom Project__c object in Salesforce linked to the Account and the originating Opportunity. Fields include: Project_Name__c, Project_Value__c, Status__c, Start_Date__c, End_Date__c, and Location__c. Unanet's financial connector data (if present) can be mapped to Project__c.Financial_Summary__c as a long-text area.

Unanet allows multiple Organizations to be associated with a single Individual (N:N relationship). Salesforce Contact supports a primary AccountId plus AccountContactRelation for additional associations. FlitStack migrates the primary organization as Contact.AccountId; secondary organizations become AccountContactRelation records with a Roles field. The relationship type from Unanet is preserved in AccountContactRelation.Roles.

Unanet activity logs for calls, emails, and meetings map to Salesforce Task (Type = Call/Email) and Event records respectively. Original timestamps, owners, and parent-record links (ContactId, OpportunityId) are preserved. Unanet notes map to Salesforce Notes (the enhanced Notes object, not legacy Note). Attachments referenced in Unanet notes are re-uploaded to Salesforce Files and linked.

Unanet file attachments on any record (Individual, Organization, Pursuit, Proposal) re-upload to Salesforce Files. ContentVersion stores the binary; ContentDocumentLink associates the file to the target Salesforce record (Contact, Account, or custom object). Salesforce's 25MB per-file limit is enforced; files exceeding this are flagged before migration and handled as external links stored in a custom URL field.

Unanet Organizations often have multiple office locations stored inline. The primary location becomes the Account billing/shipping address fields on Account. Secondary locations are migrated as Location__c custom object records linked to the Account. Each Location__c record stores: Location_Name__c, Street__c, City__c, State__c, Postal_Code__c, Country__c, and Is_Primary__c.