Migrate from Fulcrum Snap to Salesforce Sales Cloud

Fulcrum Snap's Client record maps directly to a Salesforce Account. Client name becomes Account.Name, industry can be mapped via value mapping, and client status maps to Account.Active__c (a custom field). Multi-office clients require deciding on a single primary Account or using Account Hierarchy (ParentId) for branch structure.

Fulcrum Snap's Matter has no native Salesforce equivalent. Salesforce Cases model matters but lack billing-specific fields. We recommend a custom Matter__c object with fields for matter_number, client (lookup to Account), responsible_attorney (lookup to User), billing_status, and matter_type. If your team uses Cases for a different process, Matter__c keeps legal data separate.

Fulcrum Snap Contact maps to Salesforce Contact with AccountId as the required lookup. Client-Contact associations in Fulcrum Snap (many-to-many) translate to the AccountContactRelation object in Salesforce. Attorney and staff contacts resolve to Contacts linked to the Matter__c responsible_attorney or a custom matter-team junction object.

Fulcrum Snap user records (attorneys, billing staff, admins) map to Salesforce Users by email address. Unmatched users are flagged before migration — the team either provisions Salesforce licenses and creates user records first or assigns records to a fallback owner. Active/inactive status in Fulcrum Snap maps to Salesforce User.IsActive.

Fulcrum Snap time entries (date, duration, description, matter link, user) map to Salesforce Tasks. The Task.WhatId links to the migrated Matter__c record. Original entry timestamps are preserved as Task.ActivityDate and a custom Original_Entry_Date__c field. Task.Subject and Task.Description carry the billable description and matter reference from Fulcrum Snap.

Fulcrum Snap invoice and WIP records translate to Salesforce Opportunity records with custom billing fields (Matter_Billing_Status__c, WIP_Amount__c, Invoice_Number__c, Billed_Amount__c). Each Matter maps to one Opportunity representing the full billing cycle. If your firm bills by matter as a whole, the Opportunity Amount carries total fees; if billing is per time-entry, line items map to OpportunityLineItems via a custom Price Book.

Fulcrum Snap extended client properties (e.g., billing_arrangement, practice_area, matter_counter) map to custom Account fields (e.g., Billing_Arrangement__c as a pick-list, Practice_Area__c as text, Matter_Count__c as number). Each extended field requires a corresponding __c custom field on the Account object in Salesforce before migration.

Fulcrum Snap matter-specific custom fields such as conflict_check_status, engagement_letter_date, billing_plan, and any other extended properties migrate as custom fields on the Matter__c object. Salesforce naming conventions require the __c suffix on all custom fields. Relationship fields between matters, such as parent_matter or related_matter, map to Matter__c lookup fields like Parent_Matter__c or Related_Matter__c to preserve hierarchical and associative data structures in Salesforce.

Files attached to Fulcrum Snap matters (engagement letters, invoices, documents) are downloaded and re-uploaded as Salesforce Files (ContentDocumentLink on the corresponding Matter__c or Account). Salesforce's 25MB per-file limit applies; files exceeding this are flagged before migration. File metadata (original filename, upload date, attached_by user) is preserved as custom fields on ContentVersion.

Fulcrum Snap billing line items (time entries, expenses, flat fees) split into Salesforce OpportunityLineItem records. Each line maps to a Product2 entry in the Price Book. Flat fees map as single line items with quantity=1; time-based fees require a custom Price Book entry per fee type. The split preserves the relationship between each line item and the parent Opportunity (Matter).