CRM migration
Field-level mapping, validation, and rollback between eBrief Ready and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
eBrief Ready
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between eBrief Ready and Freshsales.
Complexity
BStandard
Timeline
3–5 days
Overview
eBrief Ready and Freshsales occupy different functional domains: eBrief Ready is a document-centric platform built for legal practitioners managing briefs, court books, and multi-party litigation matters; Freshsales is a structured CRM with Leads, Contacts, Accounts, Deals, and custom modules. There is no native object-to-object equivalence, so every migration requires deliberate schema design rather than simple field mapping. We extract Matters, Parties, Documents, Annotations, Tags, and User accounts from eBrief Ready via the platform's export interface and API endpoints. We then create custom modules in Freshsales — a Matter module for legal cases, a Party module for individuals tied to each matter, and a Document module for references and metadata — before populating standard CRM objects with derived records. Party records from eBrief Ready map to Freshsales Contacts. User accounts in eBrief Ready resolve by email against Freshsales users. Document references, annotation metadata, and tagging data migrate as custom fields and Notes within Freshsales. Freshsales workflows, sequences, and automation rules do not carry over from eBrief Ready — those must be rebuilt in Freshsales Flow or skipped if your team prefers manual processes. The migration operates in a read-only window against eBrief Ready, so your team continues working in the source platform throughout. A delta-pickup window of 24–48 hours captures any records created or modified during the cutover window.
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 eBrief Ready 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.
eBrief Ready
Matter
Freshsales
Deal (Opportunity)
1:1eBrief Ready Matters have no revenue or stage concept. We map Matter to Freshsales Deal, creating an Amount field set to $0 or a configurable placeholder, and a StageName value of 'New' or your specified default. Matter status (open/closed) maps to Deal Active/Closed status. The Deal name uses the Matter title.
eBrief Ready
Matter
Freshsales
Custom Module: Matter
1:1A Freshsales custom Matter module captures legal-specific fields that Deals do not support: Matter Number, Court/Jurisdiction, Matter Type, Referring Party, and Matter Open Date. We create this module and populate it with all Matter records before linking each Matter to its corresponding Deal via a lookup field.
eBrief Ready
Party
Freshsales
Contact
1:1Party records with individual names and email addresses map directly to Freshsales Contacts. The Party display name maps to Contact FirstName + LastName (or Full Name if split is not available). Email maps to Contact Email. Phone maps to Contact Work Phone.
eBrief Ready
Party (Organization type)
Freshsales
Account
1:1Parties flagged as organizations in eBrief Ready — including law firms, chambers, courts, and opposing parties — map to Freshsales Accounts. Organization name maps to Account Name. Website URL maps to Account Website if available in eBrief Ready. A corresponding Contact record is also created and linked to the Account via AccountId.
eBrief Ready
Party–Matter link
Freshsales
Opportunity Contact Role
many:1Each party linked to a matter creates an Opportunity Contact Role linking the Contact to the Deal (Matter-as-Deal). The Party role type in eBrief Ready (e.g., Barrister, Instructing Solicitor, Expert Witness) maps to the Role pick-list value in Opportunity Contact Role.
eBrief Ready
Document metadata
Freshsales
Custom Module: Document
1:1We create a Document custom module in Freshsales to store document metadata: document name, file type, upload date, file size, and annotation count. The module links to the parent Matter via lookup. Document files themselves are re-uploaded to Freshsales Files and linked via URL custom field.
eBrief Ready
Annotation
Freshsales
Note
1:1eBrief Ready annotations export as text blocks with highlight content, tags, and date. We create Freshsales Notes attached to the corresponding Document or Contact record, using the annotation text as the Note body and the annotation date as the Note CreatedDate. Tags map to Freshsales Tags on the Note.
eBrief Ready
Tag
Freshsales
Tag
1:1Tags applied to Matters, Documents, or Parties in eBrief Ready migrate as Freshsales Tags attached to the corresponding record type. Tag names are preserved verbatim so that filtering, searching, and grouping by tag functions identically in Freshsales as it did in eBrief Ready.
eBrief Ready
User / Practitioner
Freshsales
User
1:1eBrief Ready users such as barristers, solicitors, and paralegals are resolved by matching their email address against Freshsales user accounts. Unmatched users are flagged in the migration report for your team to address. Records owned by unmatched users are assigned to a configured fallback user or left unassigned pending Freshsales account provisioning.
eBrief Ready
Workflow / Automation
Freshsales
Not migrated
1:1eBrief Ready has no standard workflow or automation engine in its core product — document processing is manual or platform-assisted. No migration of automations is applicable. Freshsales workflows must be designed and built from scratch based on your business process requirements.
eBrief Ready
Report / Dashboard
Freshsales
Not migrated
1:1eBrief Ready reporting covers document-level analytics like annotation counts and chronology exports. Freshsales reports use CRM-native objects and metrics tied to Deals, Contacts, and Accounts. The underlying data migrates successfully, but report definitions do not carry over. Your Freshsales administrator should build new reports using migrated Deal and Contact data.
eBrief Ready
Attachment / File
Freshsales
Freshsales Files
1:1Document files from eBrief Ready are downloaded and re-uploaded to Freshsales Files. Each file is linked to the parent Document record in the custom module via a URL custom field. Freshsales file size limits (25MB per file default) apply; large files are chunked or linked by reference.
| eBrief Ready | Freshsales | Compatibility | |
|---|---|---|---|
| Matter | Deal (Opportunity)1:1 | Fully supported | |
| Matter | Custom Module: Matter1:1 | Fully supported | |
| Party | Contact1:1 | Fully supported | |
| Party (Organization type) | Account1:1 | Fully supported | |
| Party–Matter link | Opportunity Contact Rolemany:1 | Fully supported | |
| Document metadata | Custom Module: Document1:1 | Fully supported | |
| Annotation | Note1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| User / Practitioner | User1:1 | Fully supported | |
| Workflow / Automation | Not migrated1:1 | Fully supported | |
| Report / Dashboard | Not migrated1:1 | Fully supported | |
| Attachment / File | Freshsales Files1: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.
eBrief Ready gotchas
No documented public API for bulk data export
File size limits on court books
Pro-tier feature gate on annotation workflows
Jurisdiction data residency locked to Australian servers
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
Extract eBrief Ready data via platform export and API
FlitStack connects to eBrief Ready using your platform credentials and exports all Matters, Parties, Documents, Annotations, Tags, and User accounts. We validate record counts against your provided inventory, flag any records with missing required fields (e.g., Parties with no email), and surface a data quality report before we begin transformation. Your team continues working in eBrief Ready during this phase — we use read-only access only.
Design and create Freshsales custom module schema
We design the Matter custom module and Document custom module based on your eBrief Ready field inventory. Each module includes the fields identified in the field mapping, with appropriate data types (text, date, pick-list, number, URL). We deliver a schema setup plan for your Freshsales admin to create the modules, or we create them via the Freshsales API if API-based setup is available for your account tier. The modules must be confirmed created before data loading begins.
Map and transform records: Matters → Deals + Matter module; Parties → Contacts + Accounts
We transform eBrief Ready data according to the object and field mapping plan. Parties become Contacts (individual) and Accounts (organization). Matters become Deals linked to the custom Matter module record. Document metadata populates the custom Document module. Annotations become Notes on the parent Document or Contact. Owner resolution maps eBrief Ready users to Freshsales users by email — unmatched owners are flagged for your team to resolve before the final migration run.
Re-upload document files to Freshsales Files and link to Document records
Document files are downloaded from eBrief Ready and re-uploaded to Freshsales Files. Each file is attached to the corresponding Document record in the custom module via a URL custom field. We apply your Freshsales file size limits and track storage consumption against your plan allocation. Files exceeding limits are flagged for manual handling or alternative storage (e.g., a shared link stored in the URL field). This step runs concurrently with record transformation where possible.
Run sample migration with field-level diff for validation
A representative slice of records (typically 50–200 across Matters, Parties, and Documents) migrates first. We generate a field-level diff showing the source value, the mapped destination field, and the resulting Freshsales value for each mapped field. You review the diff and confirm field mapping accuracy before the full run commits. Any value mapping errors (e.g., missing Role pick-list values) are corrected before proceeding.
Execute full migration with delta-pickup window and audit log
The full migration loads all validated records into Freshsales. A delta-pickup window of 24–48 hours runs after the initial load to capture any new Matters, Parties, or Documents created or modified in eBrief Ready during the cutover window. Every operation is logged in an audit trail. One-click rollback is available if reconciliation against the source data reveals discrepancies. After go-live, your team operates from Freshsales; the eBrief Ready account is retained as a read-only reference archive per your instruction.
Platform deep dives
eBrief Ready
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 eBrief Ready 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
eBrief Ready: Not publicly documented.
Data volume sensitivity
eBrief Ready 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 eBrief Ready to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your eBrief Ready 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 eBrief Ready
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.