CRM migration

Migrate from Legal Workspace to Freshsales

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

Legal Workspace logo

Legal Workspace

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between Legal Workspace and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Legal Workspace models legal work as matters linked to clients, with time entries, invoices, and document attachments forming the core record. Freshsales is a sales CRM that uses Leads, Contacts, Accounts, and Deals as its primary objects, with lifecycle stages, sales pipelines, and custom fields for extensibility. The migration maps Legal Workspace clients to Freshsales Contacts, matters to Freshsales Deals (with custom fields capturing matter type, status, and practice area), time entries to custom numeric fields or Deal Products, and invoices to a custom Invoice object or Deal-level billing fields. Document attachments re-upload to Freshsales Files. Workflows, automation rules, and billing configurations do not migrate—they must be rebuilt in Freshsales using its workflow builder. FlitStack sequences the migration by resolving owner email matches first, then migrating Accounts before Contacts, then Deals with matter metadata, ensuring foreign-key integrity throughout the load. A 24–48 hour delta-pickup window captures in-flight changes 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

Legal Workspace logo

Legal Workspace

What's pushing teams away

  • Single-tier pricing means small firms with junior fee-earners or part-time staff pay full price per seat with no entry tier.
  • UK-centric — features and compliance posture target UK firms; multi-jurisdiction firms may need a more international product.
  • Cannysoft is a smaller vendor — partner/consultant ecosystem is narrower than mainstream legal CRMs (Clio, LEAP, Actionstep).
  • No public API documentation — custom integrations require Cannysoft engagement.
  • Customers needing trust accounting at scale typically combine Legal Workspace with a separate ledger tool, since the platform's billing module focuses on time and fees rather than client account compliance.

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 Legal Workspace objects map to Freshsales

Each row shows how a Legal Workspace 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.

Legal Workspace

Client

maps to

Freshsales

Contact

1:1
Fully supported

Legal Workspace clients map directly to Freshsales Contacts. Each client contact record carries name, email, phone, and address. Clients linked to multiple matters are resolved as primary contact plus secondary relationships via Freshsales contact-to-account associations. We also preserve the original client ID in a custom field (Source_System_ID__c) for traceability, and when a client appears in multiple matters, we link them to the same Contact record to avoid duplication.

Legal Workspace

Client Organization

maps to

Freshsales

Account

1:1
Fully supported

When Legal Workspace stores a client organization (company name, industry, website), that maps to a Freshsales Account. The Account record is created first so Contact records can reference it via the AccountId lookup field. We also map the industry pick‑list value to Freshsales industry options, store the original organization ID in a custom field (Source_System_ID__c) for audit, and replicate parent‑child hierarchy using Freshsales account hierarchies.

Legal Workspace

Matter

maps to

Freshsales

Deal

1:1
Fully supported

Legal Workspace matters map to Freshsales Deals, but matter metadata (practice area, matter status, client matter ID, responsible attorney) requires custom fields on the Deal since Freshsales has no native matter concept. Each matter type becomes a separate deal pipeline in Freshsales.

Legal Workspace

Matter Stage / Status

maps to

Freshsales

Deal Stage

1:1
Fully supported

Legal Workspace matter statuses (Open, Pending Review, Closed Won, Closed Lost) map to Freshsales deal stage values per pipeline. Stage-enter timestamps are preserved as custom datetime fields on the Deal for audit continuity. We also capture the last status change date as a custom field (Last_Status_Change__c) and preserve any non‑standard status labels, mapping them to the nearest Freshsales stage while flagging any that require manual review.

Legal Workspace

Time Entry

maps to

Freshsales

Deal Product / Custom Field

many:1
Fully supported

Billable time entries accumulate per matter. We migrate total hours and billing rate as custom numeric fields on the Deal. If granular line items are needed, time entries merge into a custom Time_Entry__c custom object linked to the Deal, with date, attorney, hours, and rate preserved.

Legal Workspace

Invoice

maps to

Freshsales

Custom Object (Invoice)

1:1
Fully supported

Legal Workspace invoices have no native Freshsales equivalent. We create an Invoice__c custom object with fields for invoice number, amount, status, date, and linked Contact. Invoice line items become Invoice_Line_Item__c records or custom fields on the Invoice object. We map invoice status values (Draft, Sent, Paid, Overdue) to custom pick‑list options, and link each Invoice__c record to the corresponding Freshsales Contact using the Contact_Id field for relationship continuity.

Legal Workspace

Document

maps to

Freshsales

Files / Attachments

1:1
Fully supported

Documents attached to matters in Legal Workspace are downloaded and re-uploaded to Freshsales Files linked to the corresponding Contact or Deal record. File size limits (Freshsales caps files at 25MB per upload) are respected; oversized files are flagged for manual handling.

Legal Workspace

Calendar Event

maps to

Freshsales

Event

1:1
Fully supported

Legal Workspace calendar events (court dates, client meetings, filing deadlines) map to Freshsales Events. Original start/end times, attendees, and event type are preserved. All-day events map with the All-Day Event flag set. We also preserve the original timezone information in a custom field (Event_Timezone__c) and map any recurring event patterns to Freshsales recurrence settings where supported, ensuring no scheduling data is lost.

Legal Workspace

Task

maps to

Freshsales

Task

1:1
Fully supported

Tasks from Legal Workspace migrate as Freshsales Tasks with subject, due date, priority, and assigned user preserved. Tasks linked to a specific matter carry the corresponding DealId for association continuity. We also map the task status (Open, Completed, Cancelled) to Freshsales task status values and preserve any subtasks as related Task records linked to the parent task, maintaining the full hierarchy in Freshsales.

Legal Workspace

Note

maps to

Freshsales

Note

1:1
Fully supported

Matter notes migrate as Freshsales Notes with body text, author, and creation timestamp preserved. Notes are linked to the target Contact or Deal based on the Legal Workspace matter they originated from. We also migrate any note attachments as Freshsales Files linked to the note, and preserve any tags or categories from Legal Workspace as custom text fields (Note_Tags__c) to retain organizational context.

Legal Workspace

User / Attorney

maps to

Freshsales

User

1:1
Fully supported

Legal Workspace users and attorneys are resolved by email match against Freshsales users. Unmatched users are flagged before migration; the team either invites them to Freshsales or reassigns their records to a fallback user owner. We also preserve the user role and department from Legal Workspace in custom fields (User_Role__c, Department__c) so that permissions and reporting structures can be replicated in Freshsales after the migration.

Legal Workspace

Custom Field (Matter-Level)

maps to

Freshsales

Custom Field (Deal-Level)

1:1
Fully supported

Legal Workspace custom properties per matter type (e.g., court jurisdiction, filing deadline, opposing counsel) map to Freshsales custom fields on the Deal object. Field type is preserved: pick-list values become Freshsales pick-list fields, dates become date fields, text becomes text fields.

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.

Legal Workspace logo

Legal Workspace gotchas

Medium

Document templates and custom fields are configuration data, not matter data

Medium

Integrated timer entries and manual time records use different storage paths

High

No public API or developer portal

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

  • Matter-stage to deal-pipeline mapping creates schema complexity when matter types differ

    Legal Workspace matter types (Litigation, Corporate, Family Law, etc.) each carry different custom fields and workflows. Freshsales maps each matter type to a separate deal pipeline, and each pipeline can have its own stage values. When a firm has five matter types, the migration creates five Freshsales pipelines, each needing stage values defined before Deals land. We deliver a pipeline-and-stage setup plan before the data loads so the Freshsales schema is ready. If stage values are not pre-configured, Deals land without valid stage values and require manual correction after migration.

  • Billable time entries and invoices have no native Freshsales equivalent

    Legal Workspace tracks billable hours per matter and generates invoices with line items. Freshsales has no native billing module—time entries and invoices must become either custom fields on the Deal or a custom Invoice__c object with a custom Invoice_Line_Item__c relationship. Creating the custom object schema before migration is required; otherwise, hours and invoices are stored as unstructured notes or lost. We create the custom object definitions and field schema as part of the migration plan, but the fields must exist in Freshsales before data loads.

  • Contact deduplication by email can merge client records incorrectly in Freshsales

    Freshsales deduplicates contacts by email address on import. If a client has multiple matters in Legal Workspace with separate contact records sharing the same email, Freshsales merges them into a single contact. This is correct for contact deduplication but can be unexpected when the firm wants matter-level contact history preserved separately. We flag duplicate contacts before migration and surface them to the firm for review so the team decides whether to merge or keep records separate in Freshsales.

  • Document file size limits and unsupported formats block attachment migration

    Freshsales caps file uploads at 25MB per file. Legal Workspace may store documents exceeding this limit—particularly scanned briefs, discovery files, and multimedia exhibits. We identify oversized files before migration and flag them for manual handling (either upload directly in Freshsales or store in a linked Google Drive/SharePoint location with the URL stored in a custom field). We also flag unsupported file formats (e.g., Lotus Notes archives, encrypted PDFs) that cannot be re-hosted during migration.

  • Freshsales API rate limits throttle bulk imports on the Growth plan

    Freshsales imposes rate limits on the REST API—specifically 60 requests per minute on certain endpoints during active migration. For large datasets (50,000+ records), this throttles the migration throughput and extends the load window. We manage the migration in batched API calls with retry logic and exponential backoff to stay within rate limits. If the team is on the Growth plan with lower rate limits, we switch to CSV bulk import for the largest record types (Contacts, Accounts) and reserve API calls for custom objects and relationships.

Migration approach

Six steps for a successful Legal Workspace to Freshsales data migration

  1. Discover Legal Workspace data model and Freshsales target schema

    FlitStack reads your Legal Workspace data model via export or API—identifying all matter types, custom fields, time entry structures, and invoice schemas. We simultaneously map each to Freshsales standard objects, custom fields, and custom objects. We deliver a migration plan document that specifies pipeline names, stage values, custom field definitions, and the Invoice__c object schema before any data moves, including required field types and data validation rules.

  2. Create Freshsales custom fields and custom objects

    Before the migration runs, we create all required custom fields on the Contact and Deal objects (practice_area__c, billing_rate__c, total_hours__c, etc.) and deploy the Invoice__c custom object with its fields in your Freshsales sandbox or development environment. This step runs in parallel with owner resolution by email matching against Freshsales users. We also verify field-level security settings and ensure pick‑list values are configured before the data load begins.

  3. Migrate Accounts, then Contacts, then Deals with matter metadata

    We sequence the migration to respect Freshsales foreign-key dependencies. Accounts load first, then Contacts with AccountId links, then Deals with owner assignments and custom field values. Time entries aggregate into deal-level custom fields or custom Invoice__c records. Each batch runs with validation—so if a Contact references a non-existent AccountId, the record is flagged and held for resolution. If validation fails, FlitStack logs the error, retries the record after correcting dependencies, and continues with the remaining batch to minimize delays.

  4. Run sample migration with field-level diff on 100–500 records

    A representative slice of Legal Workspace records—spanning clients, matters, time entries, and invoices—migrates to Freshsales first. We generate a field-level diff comparing source values against destination field values so you can verify matter-to-deal mapping, billing field population, and owner resolution before the full run commits. After verification, we provide a discrepancy report listing any unmapped fields, missing values, or data type mismatches. You can then adjust field mappings or custom object definitions before the full migration proceeds, ensuring accuracy and completeness.

  5. Execute full migration with delta-pickup and one-click rollback

    The full Legal Workspace dataset migrates to Freshsales with all matter metadata, time entries, and invoices. A 24–48 hour delta-pickup window captures any records created or modified in Legal Workspace during the cutover window. The audit log records every operation. If reconciliation fails—missing records, incorrect stage values, or billing field errors—one-click rollback reverts the Freshsales environment to its pre-migration state.

Platform deep dives

Context on both ends of the pair

Legal Workspace logo

Legal Workspace

Source

Strengths

  • Predictable single-price model with all features included.
  • UK-specific GDPR posture and SRA-aligned workflows.
  • Customisable templates, fields, and user permissions out of the box.
  • Integrated time tracking and billing reduce tool sprawl for small firms.
  • Mobile app plus modern browser access for remote work.

Weaknesses

  • Single flat tier — no junior or part-time discount.
  • Smaller vendor; narrower consultant/partner ecosystem.
  • No public API documentation.
  • UK-centric — limited fit for cross-jurisdictional firms.
  • Trust accounting depth is limited versus dedicated legal accounting tools.
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. 2 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 Legal Workspace and Freshsales.

  • Object compatibility

    B

    2 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

    Legal Workspace: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Legal Workspace 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 Legal Workspace to Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Legal Workspace to Freshsales migrations complete in 48–72 hours of clock time for under 50,000 records. Larger firms with 500,000+ records, multiple matter types, or complex billing structures extend to 5–7 days. The longest step is creating the Freshsales custom object schema (Invoice__c, custom fields per matter type) before the data load begins. Field mapping validation across matter types also adds planning time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Legal Workspace.
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