Migrate from OneAdvanced Legal to Salesforce Sales Cloud

OneAdvanced Clients map directly to Salesforce Accounts. The firm name maps to Account.Name, and the primary contact on the Account gets the client-side contact role. Multi-address clients collapse to one primary billing address; additional locations stored as custom address fields or Account Contact Relations.

OneAdvanced Contact records map directly to Salesforce Contacts in a one-to-one relationship. Since every Contact requires an AccountId in Salesforce, FlitStack first resolves each contact's parent Client record to the corresponding migrated Account using name matching. This resolution step ensures that AccountId is populated correctly before contacts are written to Salesforce. Any contacts where the parent Client cannot be matched to an existing Account are flagged in the unresolved-contacts report for manual review and resolution.

OneAdvanced Matter is the central work unit; Salesforce Case is the closest standard object. FlitStack creates a Case for every Matter, sets a RecordType of 'Legal Matter', and populates Matter-specific custom fields (Matter_Type__c, Jurisdiction__c, Opposing_Party__c) from OneAdvanced properties. The Case.AccountId links to the client Account.

OneAdvanced supports sub-matters (a litigation matter with linked advisory sub-matters). Salesforce Case has a ParentCaseId field that maps to this — the top-level matter migrates first, then child matters reference it via ParentCaseId. Circular parentage is flagged and resolved to the most senior matter.

OneAdvanced Bills with line items, VAT treatment, and payment status have no Salesforce standard equivalent. FlitStack creates an Invoice__c custom object with a lookup to the Case (matter) and Account. Each line item becomes an Invoice_Line_Item__c record or is stored as a JSON body on the Invoice record depending on the line-item count.

OneAdvanced time entries track hours, rate, narrative, WIP/billed status, and fee earner per matter. Salesforce has no standard billable-time object. FlitStack creates a Time_Entry__c custom object with a lookup to the Case (Matter__c) and the fee-earner as OwnerId. Billable_Flag__c, Rate__c, Hours__c, and Narrative__c carry the full entry data.

OneAdvanced documents attached to matters re-upload as Salesforce Files (ContentVersion uploaded to the Case or Account). File size limits apply — OneAdvanced documents exceeding 25 MB are split or linked externally. Metadata including original filename, upload date, and author is preserved as ContentVersion fields.

OneAdvanced matter-level custom properties — such as Case_Type__c, Practice_Area__c, Court__c, or Counsel__c — migrate as custom fields on the Case object in Salesforce. FlitStack creates each custom field with the appropriate type (pick-list, text, lookup) before the data migration run.

OneAdvanced staff with time-capture permissions map to Salesforce Users by email address. FlitStack generates an unresolved-owner report before migration: any OneAdvanced staff whose email does not match an existing Salesforce User is flagged so the firm can create the Salesforce User or assign a fallback owner before the run commits.

OneAdvanced matter-opening checklists, bill-review approval chains, and compliance alert workflows rely on platform-specific configurations that have no equivalent in Salesforce's standard object model. These automated processes cannot be exported or migrated directly and must be reconstructed using Salesforce Flow, including Flow screens, decisions, and action elements. FlitStack exports every active OneAdvanced workflow definition as a structured reference document containing the workflow name, triggering conditions, approval stages, and associated field values, providing the firm's Salesforce administrator or implementation partner with a complete blueprint for rebuilding each process in Flow.