CRM migration

Migrate from Smokeball to HighLevel

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

Smokeball logo

Smokeball

Source

HighLevel

Destination

HighLevel logo

Compatibility

100%

12 of 12

objects map 1:1 between Smokeball and HighLevel.

Complexity

BStandard

Timeline

2–3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Smokeball organizes a law firm's data around Matters (legal cases), with Contacts, Staff, Activities, and Documents nested under each matter, plus integrated billing and trust accounting. HighLevel is an all-in-one CRM and marketing automation platform built for agencies and service businesses — it has no native legal billing, matter-type, or trust-accounting constructs. FlitStack AI migrates Smokeball data by mapping Contacts to HighLevel Contacts directly, mapping Matters to HighLevel Opportunities with a legal-matter custom field layer, re-uploading document metadata and file references, and creating a Trust Accounting custom object for ledgers that cannot collapse into standard fields. Time entries migrate as a custom object with billable-hours and rate fields preserved for reference reporting. All Smokeball workflows, matter-stage automation rules, and email templates do not transfer — we export their definitions as a rebuild reference for HighLevel's Workflow builder. Smokeball's API requires partner-program enrollment, uses OAuth 2.0, and relies on polling rather than webhooks for change detection, which shapes how we run delta-pickup during cutover.

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

HighLevel logo

HighLevel

What's pulling them in

  • Agencies choose HighLevel to consolidate CRM, email, SMS, scheduling, and funnels into one subscription, eliminating monthly bills for five to ten separate SaaS tools they previously stitched together.
  • The flat-rate pricing model bills per sub-account rather than per contact, so growing a contact database from 1,000 to 100,000 records does not trigger a billing surprise—a common pain point avoided by migrating customers.
  • White-label and sub-account capabilities let agencies resell HighLevel access to their own clients, turning a software cost center into a recurring revenue stream that justifies the subscription.
  • The platform ships a 14-day free trial with no credit card required, giving teams a low-friction entry point to validate fit before committing to the $97/month Starter tier.
  • Marketing agencies managing multiple client accounts use sub-accounts to maintain data isolation per client while operating under a single agency billing relationship with HighLevel.

Object mapping

How Smokeball objects map to HighLevel

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

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

Smokeball

Contact

maps to

HighLevel

Contact

1:1
Fully supported

Smokeball contacts (clients, opposing parties, attorneys, vendors, and witnesses) map directly to HighLevel Contacts with all standard fields preserved including names, email addresses, phone numbers, postal addresses, and contact types. Contacts with no firm affiliation receive a default Company record in HighLevel to maintain referential integrity. Duplicate detection runs on email address during import to prevent creating multiple records for the same individual across different matters.

Smokeball

Matter

maps to

HighLevel

Opportunity

1:1
Fully supported

Smokeball matters map to HighLevel Opportunities using a legal-matter custom field layer that preserves legal-specific metadata. The matter number becomes the opportunity name prefix, and matter type maps to the opportunity Stage within a dedicated Legal Pipelines setup that mirrors Smokeball's matter lifecycle stages. Matter-stage automation rules do not transfer and must be rebuilt as HighLevel Workflow triggers by the firm's admin after migration completes.

Smokeball

Matter

maps to

HighLevel

Custom Object (Legal Matter)

1:1
Fully supported

Legal-specific matter fields — debtor information, opposing attorney, other-side party, matter responsible attorney, person assisting, and internal reference numbers — have no HighLevel native equivalent. We create a Legal Matter custom object with up to 10 unique fields and associate it to the corresponding Opportunity via a many-to-one link. This preserves the complete legal context for each matter without requiring staff to reference external Smokeball records.

Smokeball

Staff

maps to

HighLevel

User / Custom Field

1:1
Fully supported

Smokeball staff (attorneys, paralegals, admins, and billing coordinators) are matched by email to HighLevel users where possible. Staff without a HighLevel login — such as departed attorneys or historical assignees — are stored as a Staff_Record__c custom field on relevant Opportunities so historical attribution is preserved. Active staff receive HighLevel user seats and appear as Opportunity Owners on matters assigned to them.

Smokeball

Activity (Task)

maps to

HighLevel

Task

1:1
Fully supported

Smokeball activity entries — tasks, document work, memos, emails, and matter admin activities — map to HighLevel Tasks with original timestamps, assigned staff, and matter linkage preserved. The activity type maps to the Task Type pick-list in HighLevel, and each task retains its parent matter association through the Opportunity link on the related Legal Matter custom object record.

Smokeball

Document

maps to

HighLevel

Attachment / Custom Object

1:1
Fully supported

Smokeball documents cannot be transferred as binary files due to platform API limitations. We re-upload document metadata (document name, matter association, document type, author, creation date, and Smokeball document ID) to HighLevel Attachments on the relevant Opportunity. The firm uploads actual files post-migration using HighLevel's document upload interface, guided by a document re-upload checklist ordered by matter number.

Smokeball

Time Entry

maps to

HighLevel

Custom Object (Billable Time)

1:1
Fully supported

Smokeball time entries (date, hours, billing rate, total amount, and descriptive notes) have no native HighLevel equivalent since HighLevel lacks a billing module. We create a Billable Time custom object linked to the parent Opportunity, preserving the complete financial record for reference and reconciliation against the firm's standalone accounting software. Time entries remain accessible for historical reporting without requiring manual re-entry.

Smokeball

Trust Accounting Ledger

maps to

HighLevel

Custom Object (Trust Accounting)

1:1
Fully supported

Smokeball trust accounting ledgers (funds held, transaction history, client-matter association, and running balances) have no HighLevel equivalent. We create a Trust Accounting custom object with fields for ledger balance, transaction type, transaction date, and matter reference. The firm reconciles against their dedicated trust accounting tool post-migration to ensure compliance with legal accounting requirements.

Smokeball

Contact Tag

maps to

HighLevel

Tag

1:1
Fully supported

Smokeball contact tags (client type, matter involvement, staff role, referral source, and billing status) map directly to HighLevel Tags with values preserved exactly as they appear in Smokeball. Tags on matter-associated contacts are preserved at the contact level in HighLevel, allowing firms to filter and segment their contact database using the same taxonomy they established in Smokeball. Multi-word tags with spaces are supported.

Smokeball

Matter Type

maps to

HighLevel

Custom Field / Pipeline Stage

1:1
Fully supported

Smokeball matter types (Family Law, Personal Injury, Real Estate, Estate Planning, Criminal Defense, and other practice-area classifications) map to a Matter_Type__c custom pick-list on the Legal Matter custom object, with values mapped one-to-one from Smokeball. If a firm uses fewer than five matter types, we may use HighLevel Pipeline stages instead for simpler pipeline reporting and visualization across the CRM dashboard.

Smokeball

Hard Cost / Soft Cost

maps to

HighLevel

Custom Object (Disbursements)

1:1
Fully supported

Smokeball hard costs (court filing fees, expert witness fees, medical record retrieval charges) and soft costs (photocopying, postage, courier delivery, long-distance calls) have no HighLevel equivalent. We create a Disbursements custom object linked to the parent Opportunity, capturing cost type, amount, supplier/vendor name, and whether it is billable to the client as a pass-through expense. Disbursement records allow firms to track case-related expenses separate from professional time charges.

Smokeball

Workflow Template

maps to

HighLevel

Workflow (manual rebuild required)

1:1
Fully supported

Smokeball workflow templates auto-generate tasks, assign staff, and advance matter stages — this logic cannot transfer to HighLevel because HighLevel Workflows use a different trigger-action architecture and are scoped to contacts and opportunities, not matters. We export workflow definitions as a structured reference document for the firm's HighLevel admin to rebuild using HighLevel's Workflow builder with the original Smokeball logic as a specification.

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

HighLevel logo

HighLevel gotchas

High

Sub-account architecture creates isolated data silos per client

High

Usage-based telecom and AI costs are not in the subscription price

Medium

Workflows have no native equivalent in most destination CRMs

Medium

API rate limits cap bulk migration throughput at 100 requests per 10 seconds per sub-account

Low

White-label configuration and branding assets do not export via API

Pair-specific challenges

  • Trust accounting ledgers and billing records have no native HighLevel equivalent and require a dedicated custom object schema

    Smokeball's trust accounting module tracks client funds, transaction history, and ledger balances — critical for legal compliance. HighLevel has no native trust accounting construct. FlitStack AI creates a Trust Accounting custom object with Ledger_Balance__c, Transaction_Type__c, Transaction_Date__c, and Amount__c fields, linked to the parent Legal Matter Opportunity. The firm must reconcile this against their dedicated trust accounting tool (or LawPay) post-migration. A failed trust accounting mapping creates a regulatory exposure for the firm, which is why we treat it as high-severity.

  • Smokeball workflows and matter-stage automation templates cannot transfer to HighLevel's Workflow engine

    Smokeball workflow templates attach to matter types and auto-generate tasks, assign staff, and advance matter stages using a rule-based engine specific to Smokeball's matter lifecycle. HighLevel Workflows use trigger-action chains scoped to contacts and opportunities — they cannot receive Smokeball's workflow definitions. We export Smokeball workflow templates as a structured JSON document so the firm's HighLevel admin can rebuild them in the HighLevel Workflow builder. Firms that skip this step lose all automated task generation on new matters.

  • Smokeball's API requires partner-program enrollment and has no webhook support, affecting delta-pickup reliability

    The Smokeball API is not self-serve — firms must enroll in the Smokeball partner program to obtain a client_id and client_secret. Additionally, Smokeball's API has no documented webhooks or event subscriptions; change detection relies entirely on polling. Rate limits are not publicly documented. FlitStack AI enrolls as a partner, requests an access token via OAuth 2.0, and implements polling at conservative intervals to avoid triggering undocumented throttling. The delta-pickup window (24–48 hours) is sized accordingly.

  • HighLevel custom objects cap at 10 per sub-account with 10 unique fields each — legal schemas can exceed these limits

    HighLevel's custom object model limits each sub-account to 10 custom objects, each with up to 10 unique fields. A law firm with trust accounting ledgers, billable time entries, disbursements, legal matter metadata, and document records can approach or exceed these limits. FlitStack AI audits the firm's Smokeball schema before migration and advises on collapsing low-cardinality records into single multi-value custom fields or deferring archival data to preserve headroom for active-migration objects.

  • Document files cannot be migrated as binary blobs — only metadata transfers, with files re-uploaded post-migration

    Smokeball stores documents as binary files inside the platform, often assembled automatically via the Smokeball Toolbar and Word integration. HighLevel stores files as Attachments on contacts and opportunities but does not have a document assembly or template automation equivalent. FlitStack AI migrates document metadata (document name, type, creation date, matter association) to HighLevel Attachment records. The actual files must be re-uploaded by the firm post-migration. Firms with large document libraries should budget staff time for this step.

Migration approach

Six steps for a successful Smokeball to HighLevel data migration

  1. Audit Smokeball schema and build the migration map

    FlitStack AI reviews the firm's Smokeball data — counting matters, contacts, staff records, documents, time entries, trust ledgers, and workflow templates. We map each object and field to its HighLevel destination (Contact, Opportunity, Legal Matter custom object, Billable Time custom object, Trust Accounting custom object, or Disbursements custom object). We flag schema items that exceed HighLevel's 10-custom-object limit and propose consolidation. The firm approves the mapping before any data moves.

  2. Enroll as Smokeball API partner and authenticate

    FlitStack AI registers as a Smokeball partner to obtain OAuth 2.0 credentials (client_id and client_secret). We authenticate via the Smokeball token endpoint using the appropriate grant type. With credentials in hand, we begin polling the Smokeball API for matters, contacts, staff, time entries, and trust accounting records. We use conservative polling intervals because Smokeball does not publish rate-limit headers. The firm's data remains fully accessible in Smokeball throughout this phase.

  3. Create HighLevel custom objects, custom fields, and pipelines

    We create the HighLevel custom objects required by the migration map — Legal Matter, Billable Time, Trust Accounting, and Disbursements — within the firm's sub-account. We create custom fields on each object (up to 10 unique fields per object) and set up a Legal Pipelines with stages matching the firm's Smokeball matter types. We configure the pipeline before data lands so that Opportunities and their associated custom object records can be created in the correct structure from the first import.

  4. Run a sample migration and validate field-level accuracy

    A representative slice of Smokeball data — typically 50–200 matters across multiple matter types, plus associated contacts, time entries, and trust ledger records — migrates to HighLevel first. We generate a field-level diff showing every source field value alongside its HighLevel destination. The firm reviews trust accounting mapping, billable time preservation, matter-stage assignment, and staff attribution before the full run commits.

  5. Execute full migration with delta-pickup window

    The full migration runs against HighLevel's API with all Smokeball records mapped to their destination objects. A 24–48-hour delta-pickup window captures any Smokeball records modified during the cutover period. Document metadata migrates to HighLevel Attachment records; the firm receives a document re-upload checklist for post-migration file restoration. An audit log records every record created, updated, or skipped, and one-click rollback is available if reconciliation identifies data integrity issues.

  6. Deliver workflow export and post-migration reconciliation report

    We deliver a structured export of all Smokeball workflow template definitions (trigger conditions, task assignments, matter-stage rules) as a JSON reference document. The firm's HighLevel admin uses this to rebuild automations in HighLevel's Workflow builder. We also deliver a reconciliation report comparing Smokeball record counts against HighLevel record counts by object, flagging any gaps for manual review. Trust accounting and time entry totals are reconciled against the firm's target accounting tool.

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.
HighLevel logo

HighLevel

Destination

Strengths

  • Consolidates CRM, marketing automation, email, SMS, scheduling, and funnels into one platform at a predictable flat monthly rate.
  • Supports unlimited contacts and unlimited users on all paid tiers, removing per-record billing anxiety as databases grow.
  • Offers white-label and sub-account capabilities that let agencies resell access and manage multiple client environments under one billing relationship.
  • Includes built-in review management, reputation monitoring, and AI agents as native features rather than third-party add-ons.
  • Exports Contacts and Companies via a scalable async bulk CSV system that handles multi-million-row datasets without blocking the UI.

Weaknesses

  • The breadth of features creates a steep learning curve; advanced automations and Workflow configuration require significant time investment that smaller teams may not recover.
  • The platform charges usage-based fees for telecommunications and AI features that are not included in the base subscription, leading to bill surprises.
  • Recurring user reports on Reddit and G2 describe bugs, errors, and slow support response times that disrupt live marketing and sales operations.
  • Sub-account architecture, while powerful for agencies, adds migration complexity when identifying which client data lives in which isolated environment.
  • The platform is designed for agencies and SMBs; larger enterprises requiring deep reporting, custom objects at scale, or complex role-based access may outgrow its capabilities.

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 HighLevel.

  • 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 HighLevel 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 HighLevel data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Smokeball-to-HighLevel migrations complete in 2–3 weeks for firms with under 5,000 matters and contacts. Firms with 10,000+ matters, trust accounting ledgers, multiple staff assignments per matter, or large document libraries extend to 4–6 weeks. The longest planning step is designing the custom object schema for legal-specific data (trust ledgers, billable time, disbursements) that has no native HighLevel equivalent. Smokeball API enrollment and authentication typically adds 3–5 business days before migration engineering begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Smokeball.
Land in HighLevel, 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