CRM migration

Migrate from Smokeball to Salesforce Sales Cloud

Field-level mapping, validation, and rollback between Smokeball and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.

Smokeball logo

Smokeball

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

93%

13 of 14

objects map 1:1 between Smokeball and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Smokeball organizes law-firm data around matters and activities: clients, opposing parties, attorneys, documents, time entries, trust ledger entries, and workflow tasks. Salesforce Sales Cloud uses Account-Contact-Opportunity with Case for service work and custom fields for extensibility. There is no native matter concept in Salesforce—the migration must decide per record whether a Smokeball matter becomes a Salesforce Account (for the client organization), a Case (for active legal work), an Opportunity (for business development), or some combination. We map Smokeball contacts to Salesforce Contacts attached to Accounts, staff to Salesforce Users by email match, and documents to Salesforce Files. Trust accounting balances and hard/soft costs become custom fields on Account since Salesforce has no native trust-ledger construct. Smokeball workflows do not migrate—they must be rebuilt in Salesforce Flow using an exported definition. The migration uses a staged approach: first staff and clients (so owner lookups resolve), then matters with their contacts, then time entries and documents, with a 24–48 hour delta window at cutover to capture in-flight work.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Smokeball logo

Smokeball

What's pushing teams away

  • Billing issues appear in 22+ G2 reviews, with users reporting disorganization in invoicing, problems with payment routing, and hard/soft cost misalignments between Smokeball and integrated accounting software like Xero or MYOB.
  • Missing features frustrate users, particularly poor search functionality across documents and the absence of auto-save, which leads to lost work and wasted time re-entering data.
  • Software bugs cause real operational pain—duplicate documents appearing in containers, slow performance under load, and files failing to load after upload, each cited 14+ times on review platforms.
  • Collaboration limitations and cumbersome document import processes are cited as missing features, making it difficult for multi-attorney firms to share and organize files efficiently.
  • Integration issues with third-party software, particularly after major updates, cause connectivity failures with Outlook, LawPay, and accounting tools that disrupt billing workflows.

Choosing

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Smokeball objects map to Salesforce Sales Cloud

Each row shows how a Smokeball object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Smokeball

Staff

maps to

Salesforce Sales Cloud

User

1:1
Fully supported

Smokeball staff records (first name, surname, email, status, salutation) map to Salesforce User records. Email match is the primary key for owner resolution. Active Smokeball staff become active Salesforce Users with appropriate ProfileId; inactive staff become inactive Users. RoleId assignment follows the person's practice area if available.

Smokeball

Contact (Client)

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

Smokeball contacts linked as clients map to Salesforce Contacts. Each contact requires an AccountId lookup—Smokeball contacts without a primary organization attach to a default 'Individual Client' Account or the contact's address becomes Account.Name. Phone, email, address fields map directly. Tags migrate as a custom multi-select picklist.

Smokeball

Contact (Opposing Party, Opposing Attorney)

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

Non-client contacts (opposing parties, opposing attorneys) map to Salesforce Contacts on a separate Account representing the opposing organization, or as individual Contacts attached to a generic 'Opposing Party' Account if no organization exists. The contact's relationship to the matter is preserved in a custom Role__c field on Contact.

Smokeball

Matter

maps to

Salesforce Sales Cloud

Account + Case + Opportunity (split)

1:many
Fully supported

Smokeball matters do not map to a single Salesforce object. We split each matter into: (1) an Account representing the client organization, (2) a Case for active legal work, and (3) optionally an Opportunity if the matter has a billing relationship. Matter type determines which RecordTypeId is assigned for page layout scoping. Person Responsible maps to Case.OwnerId by email match.

Smokeball

Matter Type

maps to

Salesforce Sales Cloud

RecordTypeId + Custom Field

1:1
Fully supported

Smokeball matter types (family law, personal injury, estate planning, etc.) become Salesforce Record Types on Case and Account. Each Record Type enables a different page layout with type-specific pick-list values. The original Smokeball matter type is preserved in a Matter_Type__c custom field for reporting continuity.

Smokeball

Activity (tasks, memos, emails)

maps to

Salesforce Sales Cloud

Task

1:1
Fully supported

Smokeball activities—tasks, document work, memos, emails—are logged as Salesforce Tasks. The original timestamp, owner (mapped by email), and subject are preserved. Task.WhatId links to the related Case or Opportunity. Task status defaults to 'Completed' for historical records. Reminder dates and priorities also migrate to maintain the original activity context for audit review.

Smokeball

Time Entry

maps to

Salesforce Sales Cloud

Task + Custom Fields

1:1
Fully supported

Smokeball time entries (hours, description, date) become Salesforce Tasks with Type='Time Entry' plus custom fields Duration_Hours__c and Billing_Rate__c. AutoTime-generated entries preserve their source flag in a custom field. Time entries billable flag maps to a custom Is_Billable__c checkbox. Historical billing rates also migrate for reporting on client cost recovery and attorney utilization metrics.

Smokeball

Document / File

maps to

Salesforce Sales Cloud

ContentDocument + ContentVersion

1:1
Fully supported

Smokeball documents upload to Salesforce Files (ContentDocument/ContentVersion). Document Containers become Salesforce Libraries if the firm uses ContentWorkspace. Files are linked to the relevant Case via ContentDocumentLink. Inline images in notes are downloaded and re-hosted in Salesforce. Maximum file size is 25 MB per Salesforce default limit.

Smokeball

Trust Accounting (balance, entries)

maps to

Salesforce Sales Cloud

Custom Fields on Account

1:1
Fully supported

Smokeball trust account balances and ledger entries have no Salesforce native equivalent. We create custom fields on Account: Trust_Balance__c (Currency), Trust_Ledger_Entries__c (Long Text Area for audit reference), and Trust_Account_Number__c (Text). The original trust entries are preserved as a JSON blob in the text area for compliance reference.

Smokeball

Debtor / Open Balance

maps to

Salesforce Sales Cloud

Custom Fields on Account + Opportunity

1:1
Fully supported

Smokeball debtor fields (open debtors balance, other side, other side attorney) become custom fields on Account: Open_Debtors_Balance__c, Other_Side__c, Other_Side_Attorney__c. If the matter generated billing opportunities, the outstanding balance also appears on the related Opportunity via Outstanding_Balance__c. Collection status can be tracked using a custom picklist field for follow-up workflow automation.

Smokeball

Hard Costs / Soft Costs

maps to

Salesforce Sales Cloud

Custom Fields on Case or Account

1:1
Fully supported

Smokeball's hard costs (court filing fees, expert fees—paid to third parties) and soft costs (photocopying, postage—firm overhead) map to custom Decimal fields on Case: Hard_Costs__c and Soft_Costs__c. Whether these live on Case or a custom Cost_Tracking__c object depends on the firm's reporting requirements, decided during the mapping session.

Smokeball

Matter Number / Internal Reference

maps to

Salesforce Sales Cloud

Case.CaseNumber + Custom Field

1:1
Fully supported

Smokeball matter number and internal reference map to Case.CaseNumber and a custom Original_Matter_Number__c text field. Salesforce auto-generates CaseNumber, but we preserve the original Smokeball identifier for continuity and audit purposes. The custom field enables users to search by the legacy matter number directly from Salesforce without relying on the system-generated case number format.

Smokeball

Person Assisting

maps to

Salesforce Sales Cloud

Case.OwnerId + Custom Field

1:1
Fully supported

Smokeball's Person Assisting field (secondary staff on a matter) maps to a custom Person_Assisting__c lookup field on Case pointing to User. The primary Person Responsible maps to Case.OwnerId. Both resolve by email match to Salesforce Users before migration runs. This allows multiple attorneys to be associated with a single matter while maintaining clear primary responsibility assignments.

Smokeball

Workflows

maps to

Salesforce Sales Cloud

Flow

1:1
Mapping required

Smokeball workflows are series of tasks tied to matter types. They do not have a Salesforce equivalent—Flow is the only automation engine in Salesforce in 2026, and workflow definitions are not portable. We export the workflow definitions as a reference document for the firm's Salesforce admin to rebuild in Flow Builder. The tasks themselves (created by workflows) migrate as completed Tasks.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Smokeball logo

Smokeball gotchas

High

Document upload may not finish before Go Live

High

Data entry must halt during final LIVE migration cutover

Medium

Duplicate contacts are not detected during import

Medium

Closed and archived matters migrate after Go Live

Medium

Lower pricing tiers strip PDF functionality and auto time

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • Matter-to-object split creates schema complexity before data lands

    Smokeball matters bundle client, opposing party, billing, trust balance, and activities into one record. Salesforce has no matter object—each matter must be decomposed into an Account (client organization), a Case (legal work), and optionally an Opportunity (billing relationship) before data can insert. The Matter_Type__c value determines which RecordTypeId applies to the Case and which page layout loads. Firms with 10+ matter types end up with 10+ record types, each requiring its own page layout assignment, field-level security review, and validation rule. We deliver a record-type and page-layout setup plan before the migration runs so the Salesforce schema is ready to receive the data.

  • Contact-to-Account resolution requires pre-existing Accounts

    Salesforce requires Contact.AccountId for most standard fields and sharing rules. Smokeball contacts can be linked to a Matter without belonging to a company organization—particularly opposing parties and individual clients. We resolve this by creating an Account for every Smokeball contact that lacks a parent organization, using the contact's name as the Account.Name. The Salesforce sharing model then functions correctly. If your firm has a large number of individual-party contacts without organizations, the Account creation step adds planning time to the migration.

  • Trust accounting has no Salesforce native equivalent

    Smokeball's trust accounting tracks client funds held in a trust ledger with separate balance fields and ledger entries. Salesforce has no native trust-ledger construct. We preserve trust balances as custom currency fields (Trust_Balance__c, Trust_Ledger_Entries__c) on the Account record, and store the full ledger history as a JSON blob in a Long Text Area field for compliance audits. Any reporting on trust activity requires Salesforce reporting on these custom fields or a separate trust accounting tool integrated via AppExchange.

  • Smokeball workflows do not migrate to Salesforce Flow

    Smokeball workflows—series of tasks applied automatically to matter types based on practice area—are not portable to Salesforce. Workflow definitions in Smokeball use a proprietary format tied to the Microsoft Word automation toolbar. Salesforce Flow is the only current automation engine (Workflow Rules and Process Builder are deprecated as of 2026). We export your Smokeball workflow definitions as a reference document so your Salesforce admin can rebuild them in Flow Builder. The individual tasks created by those workflows do migrate as completed Task records.

  • Document versioning and Document Container structure requires mapping decisions

    Smokeball Document Containers (letterheads, headers/footers) with version history map to Salesforce Libraries (ContentWorkspace) and ContentVersion versioning. If your firm relies heavily on document templates with version control, we need to know which templates should become Salesforce ContentLibrary assets versus standard Files. Template versioning is handled differently in Salesforce—ContentDocument stores current version; historical versions are accessible via ContentVersion records with VersionData. Inline images in Smokeball notes must be downloaded and re-uploaded as Salesforce Files.

Migration approach

Six steps for a successful Smokeball to Salesforce Sales Cloud data migration

  1. Audit Smokeball data and design the matter-split strategy

    We extract a full export of Smokeball data: staff, contacts, matters, activities, time entries, documents, and trust ledger entries. Our team reviews the matter types and decides per type whether the matter becomes a Case, an Account+Case pair, or an Account+Opportunity for billing-enabled matters. We map every staff member to a Salesforce User by email and flag any unmappable contacts (no email, no name) for your review. We also export Smokeball workflow definitions for reference rebuild in Salesforce Flow.

  2. Create Salesforce schema (record types, page layouts, custom fields)

    Before data moves, your Salesforce admin creates the RecordTypeId entries for each matter type, assigns page layouts per record type, and we create the custom fields identified in the mapping plan (Trust_Balance__c, Hard_Costs__c, Soft_Costs__c, Person_Assisting__c, Original_Matter_Number__c, Matter_Type__c, etc.). We deliver a schema setup checklist so the Salesforce side is ready before validation runs. This step also includes setting up ContentWorkspace libraries for document containers.

  3. Resolve owners and create placeholder Accounts

    Salesforce requires every Contact and Case to have an AccountId and OwnerId. We match Smokeball staff to Salesforce Users by email, flagging any unmatched owners for your team to either invite to Salesforce or assign to a fallback user. For Smokeball contacts without a parent organization, we create placeholder Accounts using the contact's name so Contact.AccountId resolves correctly. This step must complete before any records insert.

  4. Run sample migration with field-level diff

    A representative slice migrates first—typically 100–300 records spanning staff, contacts, matters, activities, time entries, and documents. We generate a field-level diff between the Smokeball export and the Salesforce records so you can verify owner resolution, Account creation for individual contacts, matter-split logic per type, and custom field population before the full run commits. Approval from your team on the sample diff is required before the full migration proceeds.

  5. Execute full migration with delta-pickup window

    The full migration runs in staged passes: (1) Users and Accounts, (2) Contacts with AccountId lookups, (3) Cases with RecordTypeId and owner assignment, (4) Activities and time entries linked to Cases, (5) Documents as ContentVersion + ContentDocumentLink. A delta-pickup window (24–48 hours) at cutover captures any Smokeball records created or modified during the migration run. FlitStack AI uses scoped read access on Smokeball throughout—so your team keeps billing in Smokeball during the cutover. Audit logs document every operation, and one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Smokeball logo

Smokeball

Source

Strengths

  • Automatic time tracking via AutoTime captures billable activity without manual entry, directly improving firm collection rates.
  • Comprehensive document automation with Smokeball Toolbar in Microsoft Word enables rapid generation of standardized legal precedents and letters.
  • Built-in trust accounting and reporting satisfy law firm regulatory requirements out of the box.
  • Exceptional customer support with dedicated Client Success Managers and UK-based telephone support keeps small firms operational.
  • AI assistant Archie and Outlook integration reduce context switching for attorneys managing client communications.

Weaknesses

  • Billing issues appear frequently in reviews, with payment routing and cost allocation problems requiring manual intervention.
  • Search functionality across documents and matters is a known pain point, making it difficult to locate historical files efficiently.
  • Auto-save is not available, risking data loss if attorneys forget to save manually during document work.
  • Collaboration features are limited, making Smokeball less suitable for large multi-office or multi-attorney firms requiring real-time co-authoring.
  • Price increases have been reported by existing customers, and lower tiers strip critical features like PDF functionality and automatic time tracking.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

Complexity grading

How hard is this migration?

Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Smokeball and Salesforce Sales Cloud.

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Smokeball: Not publicly documented.

  • Data volume sensitivity

    B

    Smokeball doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Smokeball to Salesforce Sales Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Smokeball to Salesforce Sales Cloud data migrations

Answers to the questions buyers ask most during Smokeball to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Smokeball to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Smokeball-to-Salesforce migrations complete in 48–72 hours for firms with under 25,000 records. Larger firms with 200,000+ records, complex document libraries, or 10+ matter types require 7–14 days. The longest planning step is the matter-split strategy—deciding which Salesforce objects receive each Smokeball matter type and configuring the corresponding RecordTypeId entries before data lands. FlitStack AI sequences the migration so foreign keys (AccountId, OwnerId, WhatId) resolve in the correct order.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Smokeball.
Land in Salesforce Sales Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day