CRM migration

Migrate from Virtual Case Management to Freshsales

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 logo

Virtual Case Management

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

12 of 12

objects map 1:1 between Virtual Case Management and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Virtual Case Management logo

Virtual Case Management

What's pushing teams away

  • Reporting and demographic tools are severely limited, making it difficult to extract meaningful business intelligence or comply with funder data requests.
  • The platform is challenging for users unfamiliar with database-style data entry, creating adoption friction for non-technical staff.
  • Agencies outgrow the platform as they scale, needing advanced workflow automation or deeper integrations that VCM does not provide.
  • Lack of flexible export options makes it difficult to move data to other systems when switching platforms.

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 Virtual Case Management objects map to Freshsales

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

maps to

Freshsales

Contact

1:1
Fully supported

VCM 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

maps to

Freshsales

Account

1:1
Fully supported

VCM 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

maps to

Freshsales

Deal

1:1
Fully supported

VCM 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

maps to

Freshsales

Deal Stage

1:1
Fully supported

VCM 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

maps to

Freshsales

User (Owner)

1:1
Fully supported

VCM 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

maps to

Freshsales

Product or Custom Fields on Deal

1:1
Fully supported

VCM 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

maps to

Freshsales

Custom Module (Referral) or Task

1:1
Fully supported

VCM'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

maps to

Freshsales

Custom Field + Sharing Rule

1:1
Fully supported

VCM 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

maps to

Freshsales

Files

1:1
Fully supported

VCM 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

maps to

Freshsales

Note or Task

1:1
Fully supported

VCM 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)

maps to

Freshsales

Custom Modules

1:1
Fully supported

VCM 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

maps to

Freshsales

Tag

1:1
Fully supported

VCM 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.

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.

Virtual Case Management logo

Virtual Case Management gotchas

High

No publicly documented bulk export API

Medium

Report definitions are not exportable

Low

Database-entry interface creates training burden

Medium

Multi-agency security level mapping requires manual verification

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

  • VCM multi-agency security levels require Freshsales Enterprise sharing-rule setup

    VCM enforces security levels that prevent agencies from viewing each other's case data. Freshsales does not have a native equivalent — security levels in VCM are enforced at the application layer, not the record level. We map security levels to a custom pick-list field (Agency_Security_Level__c) on Contact and Deal, but the actual sharing-rule configuration (field-level permissions, role-hierarchy-based access) requires Freshsales Enterprise and must be set up by your admin post-migration. This is not automated.

  • Referral network structure cannot be preserved in Freshsales without a custom module

    VCM's referral system tracks multi-step referral chains between agencies — documenting who referred whom, when, and for what specific service type across the network. Freshsales has no native referral object to capture this network structure. We can create a custom module (Enterprise plan) to store referral records with linked Contact and Account lookups, but the referral chain visualization, relationship graph, and status workflow that VCM natively provides will need to be entirely rebuilt using Freshsales Workflows, custom list views, and report builders after migration completes.

  • VCM client-to-case relationship is N:M; Freshsales deal-to-contact is 1:N

    VCM allows a single client to have multiple cases across different agencies simultaneously, and a single case can involve multiple clients — this is a true many-to-many relationship. In Freshsales, a Deal (mapped from a Case) links to one primary Contact by design. When a VCM case involves multiple clients, we create multiple deals — one per client — and link them using a custom parent-case text field to preserve the relationship. This approach can inflate the total deal count and requires your team to establish a consistent linking convention and naming strategy before migration runs in production.

  • VCM custom objects require Freshsales custom module creation (Enterprise plan only)

    If VCM is configured with custom objects beyond the standard client, case, service, and referral model — such as intake forms, compliance records, incident reports, or other specialized tracking modules — Freshsales can only store these data structures as custom modules on the Enterprise plan ($59/user/month). The Pro plan supports custom fields on standard objects but does not allow custom module creation. We identify all VCM custom objects during the discovery phase and recommend the appropriate Freshsales plan tier before migration begins to avoid scope surprises.

  • VCM file attachments require Freshsales plan storage allocation

    VCM stores documents, scanned forms, and file attachments linked to cases with no documented storage limits. Freshsales allocates file storage per user based on the plan tier: Growth includes 2GB per user, Pro includes 5GB per user, and Enterprise includes 100GB per user of storage. Large VCM instances with extensive document libraries containing case files, compliance documents, and scanned records may exceed Freshsales default storage allowances on lower tiers. We calculate total file volume and average attachment size during discovery and recommend storage add-ons or migration to Enterprise if the calculated volume exceeds available plan storage.

Migration approach

Six steps for a successful Virtual Case Management to Freshsales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Virtual Case Management logo

Virtual Case Management

Source

Strengths

  • Purpose-built for nonprofit and human services case management rather than adapted from a general CRM.
  • Referral system natively links client records across the VCM agency network without manual re-entry.
  • Multi-security-level architecture addresses inter-agency confidentiality requirements out of the box.
  • Responsive support team helps users resolve questions without extensive documentation.
  • Client auto-ID generation provides immediate record organization for new agencies.

Weaknesses

  • Reporting and analytics tools are shallow and do not meet typical funder or management reporting requirements.
  • No publicly documented bulk export or API, making data portability a significant hurdle.
  • Steep learning curve for users without database or structured data entry experience.
  • Limited customization compared to modern CRM platforms, restricting workflow adaptation as agencies grow.
  • No clear path to advanced automation or deep third-party integrations.
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 Virtual Case Management 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

    Virtual Case Management: Not publicly documented — confirmed during integration scoping..

  • Data volume sensitivity

    B

    Virtual Case Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Virtual Case Management 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 Virtual Case Management to Freshsales data migrations

Answers to the questions buyers ask most during Virtual Case Management to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most VCM-to-Freshsales migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 200,000+ records, multi-agency custom objects, or referral network structures extend to 5–7 days. The longest planning step is mapping VCM security levels and referral chains to Freshsales sharing rules and custom modules — we front-load this during discovery so the migration run itself is fast.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Virtual Case Management.
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