CRM migration
Field-level mapping, validation, and rollback between Virtual Case Management and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Virtual Case Management
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between Virtual Case Management and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Virtual Case Management targets nonprofits and social-service agencies that coordinate client care across agencies and service providers. Its data model centers on clients, cases, services, referrals, and multi-agency security levels. Freshsales is a sales CRM built around leads, contacts, accounts, opportunities, and pipelines — with contact lifecycle stages, Freddy AI scoring, and built-in telephony. The migration maps VCM's client records to Freshsales contacts and accounts, VCM cases to Freshsales deals or a custom Case Management module, and VCM services to Freshsales products or custom fields. VCM's referral network and multi-agency security tiers require custom field creation or custom module setup in Freshsales. Workflows, automation rules, and security configurations cannot migrate — we export their definitions as reference documents for Freshsales admins to rebuild using Freshsales Workflows. The migration uses scoped read access against the VCM API, a field-level diff on a sample slice, then bulk load with delta-pickup during cutover.
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 Virtual Case Management 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.
Virtual Case Management
Client
Freshsales
Contact
1:1VCM client records map 1:1 to Freshsales contacts. Each client gets a Contact record with name, email, phone, address, and custom fields for demographics. If the client has a company association in VCM, we map it to the Account lookup on the Contact record.
Virtual Case Management
Client
Freshsales
Account
1:1VCM agencies and referring organizations map to Freshsales Account records. When a client record includes agency affiliation, we create a corresponding Account and link the Contact via the primary account relationship. Multi-agency clients get one primary AccountId plus Account Contact Relationships.
Virtual Case Management
Case
Freshsales
Deal
1:1VCM cases map to Freshsales deals — case name becomes deal name, case status maps to Freshsales deal stage values, case open/close dates map to deal created_date and CloseDate. Each case generates one deal record associated with the primary client Contact.
Virtual Case Management
Case Status
Freshsales
Deal Stage
1:1VCM case status values (Open, In Progress, Pending, Closed, etc.) map to Freshsales deal stage pick-list values. We create a value-mapping table per VCM status, preserving the probability and forecast category from Freshsales stage defaults unless custom stage values are specified.
Virtual Case Management
Case Worker
Freshsales
User (Owner)
1:1VCM case workers resolve to Freshsales users by email match. If a case worker does not have a corresponding Freshsales user, we flag the record and assign it to a fallback owner (designated by your admin) so no case lands without an owner in Freshsales.
Virtual Case Management
Service Record
Freshsales
Product or Custom Fields on Deal
1:1VCM service records describe what services were delivered under a case. We map these to Freshsales Product records linked to the deal via Opportunity Line Items, or to custom multi-select fields on the Deal object — the choice depends on whether your team needs product-level revenue tracking.
Virtual Case Management
Referral
Freshsales
Custom Module (Referral) or Task
1:1VCM's referral system has no direct Freshsales equivalent. We create a custom module in Freshsales (Enterprise plan) to track referrals with fields for referring agency, referral date, referral status, and linked client Contact. If Enterprise is not the target plan, referrals migrate as Tasks with custom fields.
Virtual Case Management
Security Level / Agency Tag
Freshsales
Custom Field + Sharing Rule
1:1VCM security levels restrict case visibility by agency across the multi-agency network. We create a custom pick-list field (Agency_Security_Level__c) on the Contact and Deal objects and document sharing-rule requirements in detail. Full sharing-rule setup including field-level permissions, role hierarchies, and record-based access controls is a Freshsales admin configuration task post-migration.
Virtual Case Management
Document / File
Freshsales
Files
1:1VCM documents linked to cases download and re-upload to Freshsales Files attached to the corresponding Contact or Deal record. File size limits apply (Growth: 2GB/user; Pro: 5GB/user; Enterprise: 100GB/user). Inline images in notes are extracted and re-hosted as Freshsales Files.
Virtual Case Management
Case Note / Activity
Freshsales
Note or Task
1:1VCM case notes migrate to Freshsales Notes attached to the Contact or Deal record. Timestamps and case worker authorship are preserved in the note metadata. If VCM records time-tracked activities such as phone calls, meetings, or site visits, these map to Freshsales Tasks with Type, Subject, and duration fields set accordingly.
Virtual Case Management
Custom Objects (if configured in VCM)
Freshsales
Custom Modules
1:1VCM custom objects (used for specialized tracking like intake forms or compliance records) map to Freshsales custom modules on Enterprise plans. Custom-object relationships that use VCM's N:N model need junction objects or lookup fields in Freshsales — we document the relationship structure in the migration plan.
Virtual Case Management
Tag / Category
Freshsales
Tag
1:1VCM tags on clients and cases migrate to Freshsales Tags on the corresponding record. Freshsales uses a flat tag model — nested VCM category hierarchies are flattened to a single tag list, with the full path preserved as the tag value.
| Virtual Case Management | Freshsales | Compatibility | |
|---|---|---|---|
| Client | Contact1:1 | Fully supported | |
| Client | Account1:1 | Fully supported | |
| Case | Deal1:1 | Fully supported | |
| Case Status | Deal Stage1:1 | Fully supported | |
| Case Worker | User (Owner)1:1 | Fully supported | |
| Service Record | Product or Custom Fields on Deal1:1 | Fully supported | |
| Referral | Custom Module (Referral) or Task1:1 | Fully supported | |
| Security Level / Agency Tag | Custom Field + Sharing Rule1:1 | Fully supported | |
| Document / File | Files1:1 | Fully supported | |
| Case Note / Activity | Note or Task1:1 | Fully supported | |
| Custom Objects (if configured in VCM) | Custom Modules1:1 | Fully supported | |
| Tag / Category | Tag1: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.
Virtual Case Management gotchas
No publicly documented bulk export API
Report definitions are not exportable
Database-entry interface creates training burden
Multi-agency security level mapping requires manual verification
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
Discover VCM schema and Freshsales target plan
FlitStack AI reads your VCM configuration via scoped API access — we catalog all standard and custom objects, field types, pick-list values, and security-level configurations. We simultaneously assess your target Freshsales plan (Growth, Pro, or Enterprise) against the VCM data model to identify which features require Enterprise-tier custom modules versus Pro-level custom fields. We deliver a pre-migration schema readiness report so your Freshsales admin can create any required custom fields or modules before data loads.
Map and validate object and field relationships
We build the complete object mapping document covering Client→Contact/Account, Case→Deal, Service→Product/Custom Fields, Referral→Custom Module, and all supporting objects. A field-level mapping document captures every VCM field with its Freshsales equivalent and transformation logic. Foreign-key dependencies are sequenced correctly — Account records must exist before Contact records, and Contact records must exist before Deal records can reference them. Owner resolution logic matches VCM case workers to Freshsales users by email lookup — any unmatched owners are flagged for your admin to resolve before the migration run executes.
Run sample migration with field-level diff
A representative slice of VCM data — typically 200–500 records covering clients, cases, services, referrals, and attachments — migrates to Freshsales in a test pass. We generate a field-level diff report showing source values versus destination values for every mapped field. You review the diff to confirm security-level mapping, referral structure, and deal stage values before the full migration commits.
Execute full migration with delta-pickup
The full VCM dataset loads into Freshsales in dependency order (Agencies→Accounts, then Clients→Contacts, then Cases→Deals with service records and referrals). A delta-pickup window (24–48 hours after initial load) captures any new or modified records created in VCM during the cutover period. FlitStack AI maintains an audit log of every record created, updated, or skipped. One-click rollback is available if reconciliation fails.
Deliver workflow export and post-migration handoff
We export VCM workflow definitions, automation rules, and security configurations as structured JSON and PDF reference documents. These serve as the rebuild guide for your Freshsales admin to reconstruct automations using Freshsales Workflows (Growth: basic triggers; Pro+: time-based and field-update). The handoff package includes the field map, value-mapping tables, custom field setup instructions, and a run-book for the Freshsales admin to validate data post-migration.
Platform deep dives
Virtual Case Management
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 Virtual Case Management 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
Virtual Case Management: Not publicly documented — confirmed during integration scoping..
Data volume sensitivity
Virtual Case Management 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 Virtual Case Management to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Virtual Case Management 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 Virtual Case Management
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.