Migrate from FactBox to Salesforce Sales Cloud

FactBox matters map directly to Salesforce Accounts when the matter represents a legal client. If matters track case-specific metadata not suited to a standard Account, FlitStack creates a FactBox_Matter__c custom object so case-type pick-lists and statute dates do not pollute the commercial Account record.

FactBox contacts migrate to Salesforce Contacts with AccountId resolved by email match. If a FactBox contact has no associated matter, it lands under a default 'Unassigned Account' record. Multiple matter associations are preserved as Account Contact Relationships.

Witness is a contact with a role relative to a specific matter. FlitStack migrates the person data to Salesforce Contact and creates a FactBox_Witness_Junction__c custom object linking Contact to the Matter (Account or custom object) with a Witness_Role__c pick-list field holding FactBox's role label.

FactBox's core data element — a fact linked to a matter, a document, and optionally a witness — has no Salesforce standard equivalent. FlitStack creates a FactBox_Fact__c custom object with Lookup fields to the Matter and Contact (witness) objects, plus text fields for fact content and date.

FactBox documents are downloaded and re-uploaded to Salesforce Files (ContentDocument/ContentVersion). File size is validated against Salesforce's 25MB per-file default limit; files exceeding this are split or flagged for manual handling. Linked fact associations are preserved in a custom lookup field on the ContentVersion.

Opposing counsel in FactBox is stored as a contact with a Role='Opposing Counsel' flag. Migrated as a Salesforce Contact with a Role__c pick-list and a lookup to the Matter. The opposing counsel firm may be an Account if it is not a Salesforce user.

FactBox custom fields per matter require Salesforce custom fields with __c suffix. Pick-list values require value-mapping against Salesforce pick-list constraints. Date fields migrate directly to Salesforce Date fields. Boolean flags map to Checkbox fields.

FactBox engagement records map to Salesforce Tasks (calls, emails) and Events (meetings). Original timestamps, owners, and parent-record links are preserved. Notes migrate to Salesforce Notes (not the legacy Note object). FlitStack uses the Task WhoId / WhatId fields to link activities to the correct Contact and Matter.

If FactBox stores parent-child matter relationships (for multi-phase litigation or related cases), FlitStack creates a Parent_Matter__c lookup on FactBox_Matter__c. Circular references are flagged before migration so the hierarchy lands cleanly in Salesforce.

FactBox owner IDs are resolved by email match against Salesforce Users. Unmatched owners are flagged before migration — your team either invites them to Salesforce first or assigns their records to a fallback owner. No record lands without a Salesforce owner.

FactBox workflow sequences that route tasks or send notifications have no Salesforce equivalent. FlitStack exports the workflow definitions as a PDF plan your Salesforce admin uses to rebuild in Flow. This is always disclosed honestly and scoped separately.

FactBox reports are not migratable — the underlying data migrates but the report definitions do not. FlitStack identifies which Salesforce standard reports cover the same data and provides a rebuild reference for your Salesforce admin or Tableau analyst.