CRM migration
Field-level mapping, validation, and rollback between Centerbase and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Centerbase
Source
Freshsales
Destination
Compatibility
14 of 14
objects map 1:1 between Centerbase and Freshsales.
Complexity
BStandard
Timeline
48-72 hours
Overview
Centerbase is legal-practice-management software built around the concept of matters (cases), client records, and matter-centric billing, with workflow automation for legal processes. Freshsales is a general CRM that organizes around Leads, Contacts, Accounts, and Deals with built-in Freddy AI lead scoring, sales sequences, and multi-pipeline support. The migration carries contacts and companies into Freshsales contacts and accounts, converts matters into Freshsales deals or a custom Matter object, preserves activity history as tasks and events, and migrates custom fields. What does not move: matter-specific billing records, trust accounting, IOLTA data, workflow automations, legal templates, and reporting configurations. Those require Freshsales-side rebuild using Freshsales workflows, the Product Catalog, and native reporting. FlitStack AI sequences the load order so account-contact relationships resolve before deal associations, runs a sample migration for field-level validation, and captures a 24-48 hour delta window during cutover to pick up in-flight changes in Centerbase. During the delta window, any new or updated records in Centerbase are captured and applied to Freshsales, ensuring minimal data lag at 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 Centerbase 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.
Centerbase
Client
Freshsales
Contact
1:1Centerbase clients migrate as Freshsales Contacts. Each client record carries contact details, address, and custom fields. Client-matter relationships are preserved by mapping the primary matter to the Contact as a linked Deal so your team retains the full client history in Freshsales.
Centerbase
Client
Freshsales
Account
1:1Organizations stored as clients (corporate clients, law firm divisions) migrate as Freshsales Accounts. The Account holds the organization-level data while individual attorney contacts link to the Account, maintaining the organizational hierarchy you had in Centerbase. All standard address, phone, website, and industry fields map directly, and custom fields on the organization are transferred to the corresponding Freshsales Account custom fields.
Centerbase
Matter
Freshsales
Deal
1:1Centerbase matters map to Freshsales Deals with direct field translation for matter name, responsible attorney, opposing counsel, court information, and dates. The matter stage (open, pending, closed) translates to Freshsales deal stage values. If you have multiple matter types, each maps to a separate pipeline in Freshsales.
Centerbase
Matter
Freshsales
Custom Object: Matter__c
1:1Matters contain legal-specific fields with no Freshsales CRM equivalent: court name, case number, jurisdiction, opposing party, and legal-specific dates (filing date, discovery deadline, trial date). These require a Freshsales custom Matter object or custom fields on the Deal record. We flag these during the schema audit and deliver a field-creation plan before data lands.
Centerbase
Billing Entry
Freshsales
No Equivalent
1:1Centerbase billing entries, time slips, expense records, and LEDES-format invoices have no Freshsales equivalent. Freshsales does not include a billing or legal accounting module. These records are exported as a reference CSV and your firm rebuilds billing reporting using Freshsales Products and Deals if needed.
Centerbase
Trust Account
Freshsales
No Equivalent
1:1IOLTA and client trust account records in Centerbase do not translate to any Freshsales object. Trust accounting is a legal-specific compliance requirement that must remain in a dedicated legal accounting system. We recommend keeping Centerbase accessible in read-only mode for trust account history.
Centerbase
Custom Fields (Matter)
Freshsales
Custom Fields (Deal)
1:1Any custom fields configured on Centerbase matters migrate as custom fields on the Freshsales Deal record or in the custom Matter object. Freshsales custom fields support: text, number, decimal, date, dropdown, checkbox, multiselect, and lookup. We map each field type to the nearest Freshsales equivalent and flag any that exceed Freshsales limits.
Centerbase
Custom Fields (Client)
Freshsales
Custom Fields (Contact/Account)
1:1Custom fields on Centerbase clients migrate as custom fields on Freshsales Contacts and Accounts. If the same custom field appears on both client and matter, we create parallel fields on the Contact and Deal to maintain the data relationship. Field type mapping respects Freshsales supported types, and any picklist values are replicated so downstream automation and reporting remain consistent.
Centerbase
Document
Freshsales
File
1:1Documents attached to matters or clients in Centerbase are exported and re-uploaded to Freshsales Files linked to the corresponding Deal or Contact record. File size limits and format compatibility are checked during the export phase. Any documents that exceed Freshsales storage limits are flagged, and we provide guidance on compressing or archiving them before the migration run.
Centerbase
Calendar / Appointment
Freshsales
Event
1:1Court dates, depositions, client meetings, and deadlines stored as calendar entries in Centerbase migrate as Freshsales Events with original start and end times, owners, and linked Deal or Contact associations preserved. All event details, including location, description, and recurrence patterns, are transferred to maintain accurate scheduling and avoid double‑booking.
Centerbase
Email (Activity)
Freshsales
Task
1:1Email activities logged against matters or clients in Centerbase migrate as Freshsales Tasks with Type=Email, original timestamps, sender/recipient details, and linked Deal or Contact association maintained. The task subject line is populated from the email subject, and any attachments are recorded as file links on the task for reference.
Centerbase
Call / Note
Freshsales
Task
1:1Phone call records and attorney notes attached to matters or clients become Freshsales Tasks with the appropriate activity type and original creation timestamps. Owner assignments resolve via email matching against Freshsales users. If a call duration was recorded, it is stored in a custom numeric field on the task for reporting purposes.
Centerbase
User / Attorney
Freshsales
User
1:1Centerbase users and attorneys resolve to Freshsales users by email address. Unmatched users are flagged before migration so your team can create their Freshsales accounts or assign records to a fallback owner. We also map user roles and profiles where possible, ensuring that permission sets align with the original Centerbase access levels.
Centerbase
Workflow
Freshsales
Freshsales Workflows
1:1Matter-triggered automation rules, document merge workflows, and stage-advancement logic in Centerbase do not migrate. They require Freshsales Workflows or Sales Sequences to be configured from scratch on the destination side. We export the workflow definitions as a configuration reference. Our export includes trigger events, conditions, and action sequences so your admin can replicate the logic efficiently in Freshsales.
| Centerbase | Freshsales | Compatibility | |
|---|---|---|---|
| Client | Contact1:1 | Fully supported | |
| Client | Account1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter | Custom Object: Matter__c1:1 | Fully supported | |
| Billing Entry | No Equivalent1:1 | Fully supported | |
| Trust Account | No Equivalent1:1 | Fully supported | |
| Custom Fields (Matter) | Custom Fields (Deal)1:1 | Fully supported | |
| Custom Fields (Client) | Custom Fields (Contact/Account)1:1 | Fully supported | |
| Document | File1:1 | Fully supported | |
| Calendar / Appointment | Event1:1 | Fully supported | |
| Email (Activity) | Task1:1 | Fully supported | |
| Call / Note | Task1:1 | Fully supported | |
| User / Attorney | User1:1 | Fully supported | |
| Workflow | Freshsales Workflows1: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.
Centerbase gotchas
Images do not transfer in Centerbase report and document exports
Workflow definitions require manual rebuild on non-Centerbase destinations
Billing records carry nested LEDES codes and origination data that require explicit mapping
Trust account three-way reconciliation rules do not transfer automatically
Platform update cycles can break migrated workflows at the destination
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
Audit Centerbase data model and legal-specific fields
FlitStack AI connects to Centerbase via API and inventories all clients, matters, custom fields, activity records, documents, and user accounts. We identify which fields are legal-specific (billing, trust, court, jurisdiction) with no Freshsales equivalent and flag those for custom object or custom field creation on the Freshsales side. The audit report includes record counts per object, custom field type inventory, and a preliminary field-to-field mapping draft for your review before schema work begins.
Validate field types and build Freshsales schema plan
Based on the audit, we produce a Freshsales schema plan: custom field definitions on Deal and Contact, a custom Matter object if needed, pipeline and stage value mapping per matter type, and owner resolution mapping. Your Freshsales admin (or our team) creates the fields and pipelines in Freshsales before data migration begins. We deliver field creation instructions with exact field types, pick-list values, and UI placement so the schema matches your firm workflow terminology from day one.
Migrate Accounts and Contacts first
Freshsales requires Account records to exist before Contacts can link via AccountId. We run the accounts migration first, preserving organization names, addresses, and custom fields. Contacts migrate second, with the client-to-account lookup resolving correctly. Any unmapped attorney users are flagged for Freshsales account creation at this stage. Custom fields on both objects are populated during this phase. During this phase we also validate field-level mapping for custom fields, ensuring data types align with Freshsales field definitions and that picklist values map correctly.
Migrate Deals with matter-to-deal mapping and owner resolution
Matters translate to Freshsales Deals with direct field mapping for matter name, responsible attorney (owner), status, and dates. Legal-specific fields (court, case number, jurisdiction, opposing party) populate custom fields on the Deal or in the Matter custom object. Pipeline stage mapping is applied per matter type. Activity records linked to matters (emails, calls, notes, calendar entries) migrate as Tasks and Events with original timestamps and owner assignments preserved.
Run sample migration with field-level diff
Before committing the full migration, FlitStack AI runs a sample migration on a representative slice of 100-500 records spanning contacts, accounts, deals, and activities. We generate a field-level diff report comparing source values to destination values so your team can verify matter name mapping, custom field population, owner resolution accuracy, and date preservation. You approve the sample before the full run proceeds. Any field mapping errors are corrected before the final run.
Full migration with delta pickup and rollback readiness
The full migration commits all records to Freshsales using a sequenced load order. A delta-pickup window of 24-48 hours captures any records created or modified in Centerbase during the cutover period. FlitStack AI maintains a complete audit log of every record migrated and operation performed. If reconciliation fails or data quality issues surface post-migration, one-click rollback reverts the Freshsales instance to its pre-migration state while preserving the audit log for remediation.
Platform deep dives
Centerbase
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 Centerbase 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
Centerbase: Not publicly documented..
Data volume sensitivity
Centerbase 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 Centerbase to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Centerbase 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 Centerbase
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.