Migrate from Link app to Salesforce Sales Cloud

Link App firms map to Salesforce Accounts. Multi-contact clients (primary attorney, billing contact, matter contacts) land as one Account with a primary Contact and secondary contacts via Account Contact Relations. Account.Name and Account.Phone carry the firm name and primary phone directly. Parent-subsidiary firm hierarchies in Link App map via Account.ParentId.

Link App contacts map 1:1 to Salesforce Contacts with a required AccountId lookup to the parent Account. Each Contact record preserves the original Link App contact name, email, phone, and role (Attorney, Paralegal, Client). Contact records without a firm association are linked to a default 'Unassigned Account' or flagged for manual review before the migration commits.

Link App matter records have no native Salesforce equivalent — they are legal-matter records with billing metadata rather than revenue pipeline opportunities. FlitStack AI maps matters to Salesforce Opportunities, creating a custom Opportunity record per matter. Custom fields (Matter_Number__c, Billing_Code__c, Practice_Area__c, Responsible_Attorney__c) preserve Link App matter metadata. The Opportunity.Name uses the matter title; Amount uses the billing total or estimated value field from Link App.

Link App message records (calls, chats, emails) map to Salesforce Tasks with Type = 'Call' or Type = 'Email'. Each Task preserves the original timestamp in Task.ActivityDate, the Contact/Account link via WhoId/WhatId, and the message subject and body in Task.Subject and Task.Description. Meeting-type logs map to Salesforce Events with StartDateTime and EndDateTime matching the original Link App timestamps.

Link App annotations and case notes migrate as Salesforce Notes attached to the parent Contact or Account. The Note.Title uses the original note subject, Note.Body carries the full text, and Note.CreatedDate preserves the original creation timestamp. Rich-text formatting in Link App notes is flattened to plain text during migration to match Salesforce's Note object capabilities.

Files attached to Link App records are downloaded from Link App storage and re-uploaded as Salesforce Files (ContentDocument with ContentVersion). Each file is attached to its parent record (Contact, Account, or Opportunity) via ContentDocumentLink. File titles preserve the original Link App filename; body content is re-hosted in Salesforce's storage. Files exceeding Salesforce's 25MB per-file limit are flagged for batch splitting.

Link App stores matter metadata (Responsible_Attorney__c, Practice_Area__c, Billing_Code__c, Matter_Number__c) that does not map to standard Opportunity fields. FlitStack AI creates custom fields with the __c suffix on the Opportunity object, configures pick-list value sets where applicable, and assigns field-level security so only appropriate profiles can view billing codes.

Link App internal routing rules, notification automations, and matter-assignment workflows do not export via API and have no direct Salesforce equivalent. They must be rebuilt in Salesforce Flow by your admin or a Salesforce consultant. FlitStack AI exports a human-readable inventory of Link App automation logic as a rebuild reference document.

Link App integrations with Outlook email sync, Slack alerts, or external document management systems cannot transfer. Each integration must be re-established in Salesforce via native connectors (Salesforce for Outlook, Slack for Salesforce), AppExchange apps, or custom API connections. The integration endpoints and configuration details should be documented during the schema audit phase.

Link App user roles and access permissions (Attorney vs. Paralegal vs. Client view) have no Salesforce analogue that can be imported. Your Salesforce admin must recreate access control using Profiles, Permission Sets, and Sharing Rules. The migration delivers a role-mapping plan that translates Link App permission levels to Salesforce profile assignments.