CRM migration

Migrate from Smokeball to Freshsales

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

Smokeball logo

Smokeball

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between Smokeball and Freshsales.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Smokeball organizes legal practices around matters, clients, and document management — its data model centers on attorneys, case files, billing, and court-related workflows. Freshsales operates as a sales CRM structured around Leads, Contacts, Accounts, and Opportunities with built-in lead scoring, sales sequences, and pipeline automation. Migrating between these platforms requires collapsing a legal practice management schema into a sales-oriented object model while preserving contact records, staff assignments, and matter context that translates to account history. FlitStack AI extracts Smokeball contacts and staff via the partner-scoped API, resolves Smokeball staff members to Freshsales users by email match, and maps matter descriptions and client relationships into Freshsales Account and Contact records. The migration carries timestamps and custom fields but leaves Smokeball's document attachments, workflow templates, and billing configurations for manual rebuild in Freshsales. The migration runs in read-only API access mode — your team continues working in Smokeball during cutover with a delta-pickup window capturing any last-minute changes before go-live.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Smokeball objects map to Freshsales

Each row shows how a Smokeball object lands in Freshsales, 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

Freshsales

Contact

1:1
Fully supported

Smokeball contacts (clients, opposing counsel, third parties) map directly to Freshsales Contacts. Name, email, phone, address, and notes fields transfer 1:1. Contacts without email are flagged for manual Freshsales entry because Freshsales Create Contact API requires a valid email address.

Smokeball

Contact

maps to

Freshsales

Account

many:1
Fully supported

Smokeball contacts are often associated with organizations (law firms, opposing parties, corporate clients). The primary organization name from Smokeball contact records merges into Freshsales Account.Name, creating an Account that anchors the Contact. Multiple Smokeball contacts from the same organization create multiple Freshsales Contacts under one Account.

Smokeball

Matter

maps to

Freshsales

Account (custom fields)

1:1
Fully supported

Smokeball matters (cases, files) have no direct Freshsales equivalent. Matter description, matter type, and open debtors balance transfer as custom text fields on the related Freshsales Account — providing account history context without forcing matters into a sales deal model. Closed matters may be archived per migration scope.

Smokeball

Matter Number

maps to

Freshsales

Account.SMOKEBALL_MATTER_ID__c (custom)

1:1
Fully supported

The Smokeball matter number or internal reference identifier is stored as a custom text field on the Freshsales Account record for traceability and audit purposes. This field enables reconciliation against Smokeball source records and supports de-duplication logic if the migration runs multiple times. The custom field is indexed in Freshsales for quick lookup during reconciliation or delta-run validation.

Smokeball

Staff

maps to

Freshsales

User

1:1
Fully supported

Smokeball staff records (attorneys, paralegals, admins) resolve to Freshsales Users by email match. Each staff member's email address is compared against Freshsales user emails — matched records become the Owner for any migrated contacts or accounts they were assigned to in Smokeball. Unmatched staff are flagged for admin action.

Smokeball

Staff.Status

maps to

Freshsales

User.active

1:1
Fully supported

Smokeball staff status values (active and inactive) map directly to the Freshsales User.active boolean flag using simple value substitution. Inactive Smokeball staff are migrated as inactive Freshsales users, preserving their historical record assignments and matter associations without granting them portal or application access in Freshsales.

Smokeball

Document / Attachment

maps to

Freshsales

Freshsales Files

1:1
Fully supported

Smokeball document attachments on matters are re-uploaded to Freshsales Files, linked to the corresponding Account or Contact record. File size limits apply per Freshsales plan (2GB/user on Growth, 5GB/user on Pro, 100GB/user on Enterprise). Large document sets may require staged migration.

Smokeball

Tags

maps to

Freshsales

Contact.Tags

1:1
Fully supported

Smokeball contact tags transfer directly as Freshsales Contact Tags using a one-to-one field mapping. Tags applied to matters or staff members lack a direct Freshsales equivalent and are preserved in custom text fields on the relevant Account record where appropriate. Freshsales supports multiple tags per contact, allowing granular segmentation of migrated client data.

Smokeball

Activity (tasks, memos, emails)

maps to

Freshsales

Freshsales Activities / Tasks

1:1
Fully supported

Smokeball activity records including tasks, memos, and email communication logs associated with matters migrate as Freshsales Activities. These are attached to the corresponding Contact or Account record based on matter-to-account linkage. Original timestamps and assigning staff member details are preserved throughout the migration to maintain complete audit history.

Smokeball

Workflows

maps to

Freshsales

Freshsales Workflows

1:1
Mapping required

Smokeball workflow templates and automated task series do not migrate. They must be rebuilt in Freshsales using Freshsales Workflow automation (available on all plans with varying complexity). We export Smokeball workflow definitions as a reference document for your Freshsales admin.

Smokeball

Billing / Trust Accounting

maps to

Freshsales

N/A

1:1
Fully supported

Smokeball hard costs, soft costs, trust accounting entries, and Xero/MYOB sync configurations have no Freshsales equivalent — Freshsales has no native billing, accounting, or trust management features. Financial records should be retained in Smokeball or exported to your accounting software independently.

Smokeball

Calendar / Scheduling

maps to

Freshsales

N/A

1:1
Fully supported

Smokeball calendar entries and matter-related scheduling appointments do not have a direct equivalent in Freshsales CRM. While Freshsales supports events and tasks, it does not replicate legal practice scheduling workflows or matter-specific appointment tracking. Post-migration calendar integration with Outlook and Microsoft 365 is available through Freshsales settings and can be configured by your administrator.

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Smokeball API requires partner enrollment and has no webhooks

    Smokeball's API is not self-serve — access requires formal enrollment in the Smokeball partner program to obtain client_id and client_secret. Additionally, no webhooks are documented for Smokeball; change detection relies entirely on polling the API at regular intervals. Freshsales, by contrast, provides a documented REST API with clear rate limits (1000/hour Growth, 2000/hour Pro, 5000/hour Enterprise). FlitStack AI coordinates Smokeball partner API access as part of the migration engagement and implements polling logic within the documented Freshsales rate-limit constraints to avoid throttling during data ingestion.

  • Freshsales Create Contact API requires a valid email address

    Freshsales enforces email validation at the API level — any Create Contact request missing @ in the email field returns an error. Smokeball contacts may have incomplete or placeholder email addresses (especially for opposing counsel or third-party contacts). FlitStack AI flags all contacts without valid email before migration and routes them to a separate batch for admin review — they can be entered manually in Freshsales after migration or assigned a placeholder email that your admin replaces.

  • Matters have no direct Freshsales equivalent — context loss without custom fields

    Smokeball matters (cases, files, engagements) are the central entity in the source data model, but Freshsales has no matter or case object. Matter descriptions, matter types, open balances, opposing parties, and attorney assignments must be collapsed into Freshsales Account custom fields and Contact notes. Freshsales Account custom field limits apply per plan — Growth allows a limited number of custom fields, and Enterprise provides custom modules for higher-volume custom data. We include a custom field plan as part of the migration scope to ensure Smokeball matter context fits within Freshsales schema limits.

  • Billing and trust accounting data cannot migrate to Freshsales

    Smokeball tracks hard costs, soft costs, trust account balances, and integrates with Xero and MYOB for accounting. Freshsales has no billing, invoicing, or trust accounting module — these features are absent from every Freshsales plan. Migrating Smokeball financial data to Freshsales would result in orphaned records with no purpose. FlitStack AI advises retaining Smokeball for billing records or exporting financial data to your accounting software directly. The migration scope covers contact, account, and matter context data only.

  • Document re-upload to Freshsales Files must account for storage limits

    Smokeball document containers and file attachments are stored per matter with no explicit per-user storage cap in the platform. Freshsales assigns storage quotas by plan: 2GB per user on Growth, 5GB per user on Pro, and 100GB per user on Enterprise. Firms with large document volumes (scanned briefs, court filings, correspondence archives) may exceed Freshsales storage on lower plans. FlitStack AI inventories document file sizes during the pre-migration assessment and advises on storage provisioning or selective document migration before the full run commits.

Migration approach

Six steps for a successful Smokeball to Freshsales data migration

  1. Assess Smokeball data inventory and API access

    FlitStack AI reviews your Smokeball data inventory — counting contacts, matters, staff records, tags, and document attachments. We coordinate partner program API enrollment if not already active, confirm OAuth 2.0 credentials, and inventory custom fields configured on contacts and matters. This step produces a migration scope document listing exactly which Smokeball data objects will transfer, which will be skipped, and which Freshsales custom fields need to be created before the data run.

  2. Design Freshsales schema and custom field plan

    We map the Smokeball object model to Freshsales Contacts, Accounts, and custom fields, producing a field-level mapping document. For each Smokeball matter, we define which custom fields on the Freshsales Account will hold matter number, matter type, open balance, opposing party, and responsible attorney. We also create a Staff-to-User resolution table matching Smokeball staff emails to Freshsales user emails. Your Freshsales admin creates the custom fields and provisions user accounts before the migration run.

  3. Run sample migration with field-level diff

    A representative slice of Smokeball data — typically 100–500 records covering contacts, accounts, matters, and activities — migrates to Freshsales in a test run. We generate a field-level diff comparing source values against destination field contents, flagging any email validation failures, custom field overflows, or owner resolution gaps. You verify that Smokeball matter context is legible in the Freshsales Account records before the full migration commits. This step typically completes within 24 hours.

  4. Execute full migration with delta-pickup window

    The full Smokeball dataset migrates to Freshsales respecting Freshsales API rate limits (paginated at the plan's hourly threshold). A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in Smokeball during the cutover period. FlitStack AI logs every API operation to an audit trail. One-click rollback reverts Freshsales to its pre-migration state if reconciliation uncovers data integrity issues before you go live.

  5. Deliver reconciliation report and rebuild reference

    We deliver a post-migration reconciliation report showing record counts by object, any contacts skipped due to missing email, any matters with truncated custom field content, and the owner resolution match rate for staff-to-user mapping. We also provide an exported JSON summary of Smokeball workflow definitions as a reference document for rebuilding automations in Freshsales Workflows. Your team handles Freshsales workflow configuration, document re-upload, and Freshsales-specific integrations as post-migration setup tasks.

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

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Smokeball to Freshsales migrations complete in 3–5 days of clock time for under 25,000 contacts and 5,000 matter records. Larger matter volumes or setups with extensive document re-uploads extend to 10–14 days. The longest step is designing the Freshsales custom field schema that accommodates Smokeball matter context — that planning phase runs in parallel with your Freshsales admin configuring the target schema before any data moves.

Adjacent paths

Related migrations to explore

Ready when you are

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