CRM migration
Field-level mapping, validation, and rollback between Smokeball and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Smokeball
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Smokeball and Freshsales.
Complexity
BStandard
Timeline
3–5 days
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Freshsales
Contact
1:1Smokeball 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
Freshsales
Account
many:1Smokeball 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
Freshsales
Account (custom fields)
1:1Smokeball 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
Freshsales
Account.SMOKEBALL_MATTER_ID__c (custom)
1:1The 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
Freshsales
User
1:1Smokeball 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
Freshsales
User.active
1:1Smokeball 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
Freshsales
Freshsales Files
1:1Smokeball 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
Freshsales
Contact.Tags
1:1Smokeball 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)
Freshsales
Freshsales Activities / Tasks
1:1Smokeball 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
Freshsales
Freshsales Workflows
1:1Smokeball 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
Freshsales
N/A
1:1Smokeball 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
Freshsales
N/A
1:1Smokeball 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.
| Smokeball | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact | Accountmany:1 | Fully supported | |
| Matter | Account (custom fields)1:1 | Fully supported | |
| Matter Number | Account.SMOKEBALL_MATTER_ID__c (custom)1:1 | Fully supported | |
| Staff | User1:1 | Fully supported | |
| Staff.Status | User.active1:1 | Fully supported | |
| Document / Attachment | Freshsales Files1:1 | Fully supported | |
| Tags | Contact.Tags1:1 | Fully supported | |
| Activity (tasks, memos, emails) | Freshsales Activities / Tasks1:1 | Fully supported | |
| Workflows | Freshsales Workflows1:1 | Mapping required | |
| Billing / Trust Accounting | N/A1:1 | Fully supported | |
| Calendar / Scheduling | N/A1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Document upload may not finish before Go Live
Data entry must halt during final LIVE migration cutover
Duplicate contacts are not detected during import
Closed and archived matters migrate after Go Live
Lower pricing tiers strip PDF functionality and auto time
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Smokeball
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Smokeball and Freshsales.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Smokeball: Not publicly documented.
Data volume sensitivity
Smokeball doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Smokeball to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Smokeball to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Smokeball
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.