CRM migration
Field-level mapping, validation, and rollback between SimplyConvert and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
SimplyConvert
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between SimplyConvert and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
SimplyConvert is a legal-tech client-intake and case-management platform with a purpose-built CRM for law firms. Freshsales is a general-purpose sales CRM with Leads, Contacts, Accounts, Deals, and a custom-modules API. These platforms serve different primary use cases — legal intake vs. broad sales pipeline management — so the migration requires careful object mapping rather than a one-to-one field translation. FlitStack AI pulls data from SimplyConvert via its REST API (List Cases at 300 req/min, Get/Create Case at 2000 req/min) and maps client records to Freshsales Contacts, case files to custom Deal fields or a dedicated Cases module, and referral relationships to Account Account Relationships or junction objects. Original timestamps, document attachments, and statute-of-limitations dates transfer as custom fields. Chatbot conversation logs and lead-qualification criteria have no Freshsales native equivalent — these are flagged for manual rebuild using Freshsales Sales Sequences and workflow rules. The migration runs in read-only API mode against SimplyConvert with a 24–48 hour delta pickup window covering the cutover period.
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 SimplyConvert 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.
SimplyConvert
Client
Freshsales
Contact
1:1SimplyConvert clients (named persons with email, phone, address) map directly to Freshsales Contacts. Email, phone, and physical address fields carry over as-is. Unique client IDs are stored in Freshsales Source_System_ID__c for delta-run de-duplication. The migration uses the Source_System_ID__c field to detect and skip duplicate records on subsequent delta runs.
SimplyConvert
Client (business-type record)
Freshsales
Account
1:1Law firm names or organizational client records in SimplyConvert map to Freshsales Accounts. Company name, domain, and industry fields transfer as Account.Name, Account.Website, and Account.Industry respectively. Business-type Client records are identified during discovery by checking the client_type field for firm or organization values.
SimplyConvert
Case
Freshsales
Deal
1:1SimplyConvert cases (intake records linked to a client) map to Freshsales Deals. The case subject or claim type becomes Deal.Name. Close date and case amount (settlement value) transfer as Deal.Close_Date and Deal.Amount. Case status maps to Deal.Stage via value_mapping. Each Case-to-Deal mapping preserves the original client link as a Contact lookup.
SimplyConvert
Case Stage
Freshsales
Deal Stage
1:1Each SimplyConvert case stage (Intake, Screening, Accepted, Rejected, Settled, etc.) maps to a Freshsales deal stage pick-list value. Stage-entry timestamps migrate as custom datetime fields on the Deal for audit continuity. The value_mapping definition is delivered in the discovery report before migration begins.
SimplyConvert
Intake Form Field (custom property)
Freshsales
Custom Field on Contact / Deal
1:1SimplyConvert intake questionnaires generate dynamic custom fields per case type (trauma type, injury category, statute-of-limitations date, etc.). These map to Freshsales custom fields on the relevant Contact or Deal record. Freshsales field name and type must match the source exactly for import. A field schema snapshot is taken during discovery.
SimplyConvert
Referral Source (Client)
Freshsales
Account Account Relationship / Account
1:1When a SimplyConvert referral is already a known Client, it becomes a Freshsales Account Account Relationship (many-to-many referral tracking). When the referral is an unnamed source, it creates a Freshsales Account record with a Referral_Source__c custom field. Known firm referrals are pre-created as Account records during the pre-migration setup phase.
SimplyConvert
Document / File Attachment
Freshsales
Freshsales Files
1:1CaseHQ document uploads attach to SimplyConvert cases. These files are downloaded from SimplyConvert's API (200/min limit) and re-uploaded to Freshsales as Files linked to the corresponding Deal or Contact record. File size, format, and original upload date are all preserved during the transfer. Files are linked via the Freshsales Files API using the Source_System_ID__c for record matching.
SimplyConvert
Chatbot Conversation Log
Freshsales
Custom Field / Note / External Storage
1:1SimplyConvert's Instant Case Evaluator chatbot stores conversation logs per lead. Freshsales has no native chatbot-conversation-storage object. We can export logs as a JSON file linked to the Contact record or store them externally — your team decides based on compliance needs. The JSON export includes full transcript, criteria responses, and rejection reasons.
SimplyConvert
Lead Qualification Criteria
Freshsales
Freshsales Workflow / Sales Sequence
1:1SimplyConvert's criteria-based auto-reject logic (statute-of-limitations checks, practice-area filters) has no Freshsales native equivalent. We export the rule definitions as a rebuild reference. Your Freshsales admin recreates equivalent logic using Workflow conditions and Sales Sequences. The exported reference includes field triggers, condition operators, and resulting actions.
SimplyConvert
User / Owner
Freshsales
Freshsales User
1:1SimplyConvert users who have a valid email matching a Freshsales user account are resolved by email lookup. Unmatched owners are flagged before migration — your team either provisions Freshsales users first or assigns records to a fallback user. All owner resolution completes before the first record is written to Freshsales.
SimplyConvert
Statute of Limitations Date
Freshsales
Custom Date Field + Validation Rule
1:1SimplyConvert tracks SOL dates for each case. This transfers as a custom Date field on the Deal. A Freshsales validation rule can be configured to flag or block deals approaching their SOL date if needed. The SOL field name and date format are matched exactly from SimplyConvert during migration.
SimplyConvert
Client Create Date
Freshsales
Contact Original_Create_Date__c
1:1SimplyConvert records the original client intake date. Freshsales CreatedDate reflects the migration timestamp. We preserve the original date as Original_Create_Date__c for reporting continuity. The custom field is created as a Date type before migration so historical intake dates display correctly in Freshsales reports.
| SimplyConvert | Freshsales | Compatibility | |
|---|---|---|---|
| Client | Contact1:1 | Fully supported | |
| Client (business-type record) | Account1:1 | Fully supported | |
| Case | Deal1:1 | Fully supported | |
| Case Stage | Deal Stage1:1 | Fully supported | |
| Intake Form Field (custom property) | Custom Field on Contact / Deal1:1 | Fully supported | |
| Referral Source (Client) | Account Account Relationship / Account1:1 | Fully supported | |
| Document / File Attachment | Freshsales Files1:1 | Fully supported | |
| Chatbot Conversation Log | Custom Field / Note / External Storage1:1 | Fully supported | |
| Lead Qualification Criteria | Freshsales Workflow / Sales Sequence1:1 | Fully supported | |
| User / Owner | Freshsales User1:1 | Fully supported | |
| Statute of Limitations Date | Custom Date Field + Validation Rule1:1 | Fully supported | |
| Client Create Date | Contact Original_Create_Date__c1: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.
SimplyConvert gotchas
Per-conversion billing requires conversion-status audit before migration
No bulk export endpoint forces pagination under strict rate limits
No standalone Contact object requires structural flattening
API key generation requires direct vendor contact
Named litigation groupings not exposed as filterable objects
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
Schema discovery and referral-graph mapping
We run a read-only API scan of your SimplyConvert account to snapshot all client fields, case custom properties, document counts, and referral relationships. This discovery run identifies: which intake fields are standard vs. litigation-specific, how many referral links exist per client, whether any cases share multiple clients (common in mass torts), and what the document attachment ratio looks like. We deliver a Freshsales field-creation checklist before any data moves.
Pre-create Freshsales custom fields and referral Account structure
Your Freshsales admin (or our team) creates the custom fields identified in discovery — Trauma_Type__c, SOL_Date__c, Case_Type__c, Original_Create_Date__c, Source_System_ID__c, and any litigation-specific fields — matching the field types from SimplyConvert exactly. Referral Accounts are pre-created for known firm sources using the referral graph discovered in Step 1. No migration records are loaded until the field schema is confirmed complete via a pre-flight check against Freshsales API.
Owner and user resolution by email
SimplyConvert users are matched to Freshsales users by email address using the Freshsales Users API lookup endpoint. Any SimplyConvert user without a matching Freshsales account is flagged as an unresolved owner — your team either provisions the Freshsales user before migration or assigns those records to a fallback user designated during setup. We resolve all foreign keys before the first record is written to Freshsales to prevent orphaned case assignments.
Sample migration with field-level diff
A representative slice of 100–500 records migrates first — spanning clients, cases, referral relationships, and a sample document set. We generate a field-level diff report comparing source values against Freshsales fields so you can verify: case stage mapping correctness, custom field population accuracy, referral link resolution completeness, and document attachment integrity. Sample approval gates the full run — you sign off before the bulk migration commits.
Full migration with delta-pickup cutover
The full migration runs against Freshsales using the Bulk API for record writes and the Files API for document attachments. Documents extract at the 200/min rate in parallel with record writes to maximize throughput. A delta-pickup window (24–48 hours after the full run) captures any clients or cases created in SimplyConvert during the cutover period. An audit log records every operation with timestamps, and one-click rollback reverts Freshsales to pre-migration state if reconciliation reveals a mapping error.
Platform deep dives
SimplyConvert
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 SimplyConvert and Freshsales.
Object compatibility
2 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
SimplyConvert: 300 req/min for List Cases; 2000 req/min for Get Case and Create Case; 200 req/min for Upload Documents and Download Documents; 2000 req/min for all unspecified endpoints.
Data volume sensitivity
SimplyConvert 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 SimplyConvert to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your SimplyConvert 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 SimplyConvert
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.