Migrate from PCLaw(r) to Salesforce Sales Cloud

PCLaw clients map to Salesforce Accounts (firm/organization name) with a primary Contact record for the main billing contact. If the client is an individual attorney or solo practitioner, they map to a Contact without an Account. We preserve the original client number in Client_Number__c on the Account.

PCLaw responsible attorneys resolve to Salesforce Users via email match. Unmatched attorneys are flagged before migration so your admin can invite them to Salesforce or reassign records to a fallback owner. We preserve the attorney bar number in Attorney_Bar_Number__c custom field.

PCLaw matters map to Salesforce Opportunities with a Matter__c custom field storing the original matter number, matter type, and billing arrangement. Each matter becomes one Opportunity record. If a matter links to multiple PCLaw clients, the primary client becomes the Account; secondary clients surface via Opportunity Contact Roles.

PCLaw matter statuses (Open, Closed, On-Hold, Pending) map to Salesforce Opportunity Stage values per RecordType. We preserve the original status-transition timestamps in Status_Changed__c custom datetime fields. If your firm uses custom status labels, we map them value-by-value during the planning phase.

PCLaw billing records map to Salesforce Opportunities with line items capturing billing codes (LEDES/UBS codes), hours, rates, and tax. The Opportunity.Amount reflects the invoice total. Historical paid/unpaid status maps to Opportunity Stage progression. Trust-account-funded bills require a separate trust-disbursement mapping.

PCLaw time entries become Salesforce Tasks linked to the Matter Opportunity with a Time_Entry__c custom object storing work date, hours, billing rate, and billing status (Billable/Non-Billable). Original time-entry IDs are preserved in Source_Time_Entry_ID__c for audit continuity. Non-billable time entries map to Tasks only.

PCLaw expense entries map to a dedicated custom Expense__c object directly linked to the associated Matter Opportunity. Each expense record captures the expense category, total amount, currency code, expense date, and current billing status (Billable, Non-Billable, or Pending). Client-funded expenses that should appear on client invoices require a separate mapping to Opportunity Line Items rather than the expense object, ensuring proper invoice generation and AR tracking downstream.

PCLaw trust accounts have no Salesforce native equivalent. We create a Trust_Account__c custom object per IOLTA or client-specific trust account, storing the current balance and account type. All historical transactions (deposits, withdrawals, transfers, interest) become Trust_Transaction__c records linked to the trust account and the funding matter Opportunity.

Three-way reconciliation data—client ledger, trust ledger, and operating ledger balances—preserved in Trust_Transaction__c with transaction type, amount, date, and matter reference. Current balances stored as Trust_Balance__c on the Trust_Account__c. Your Salesforce admin uses these to build the trust-dashboard view in Lightning.

PCLaw document attachments migrate to Salesforce Files. Each file becomes a ContentVersion record linked via ContentDocumentLink to the Matter Opportunity. Legal-specific metadata (document ID, version number, author) stored as custom fields on ContentVersion since Salesforce Files lack native legal-version semantics.

PCLaw's many-to-many client-matter relationships map to Salesforce using a two-pronged approach. OpportunityContactRole records capture billing contacts and matter-specific roles for each client association. AccountContactRelation handles broader account-contact associations that span multiple matters. When a single matter involves multiple clients, the primary client becomes the Opportunity.Account value while additional clients are added as OpportunityContactRole entries with appropriate role designations such as Billing Contact or Secondary Client.

PCLaw custom fields on any object become Salesforce custom fields following the __c naming convention. Pick-list custom fields in PCLaw map to Salesforce pick-lists or multi-select pick-lists. Custom field metadata (data type, pick-list values, required/optional) is documented in the migration plan before schema creation.