CRM migration

Migrate from myCRMS.com to Freshsales

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

myCRMS.com logo

myCRMS.com

Source

Freshsales

Destination

Freshsales logo

Compatibility

67%

6 of 9

objects map 1:1 between myCRMS.com and Freshsales.

Complexity

CModerate

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from myCRMS.com to Freshsales is a migration from a lightweight, minimally-documented CRM to a structured SMB platform with built-in phone, email, chat, and Freddy AI scoring. myCRMS.com stores contacts, companies, and pipeline deals; we extract those records in dependency order, loading companies first so that Contact-to-company lookups resolve at insert time. Any custom fields discovered during the pre-migration audit are created in Freshsales before data loads begin. Activity timestamps and owner assignments transfer where the export exposes those fields. Freshsales field validation rules can reject records on import; we either disable validation temporarily or pre-clean field formats during the transform phase. Workflows, Smart Lists, and any automation logic do not migrate; we deliver a written inventory of what the admin must rebuild in Freshsales.

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

myCRMS.com logo

myCRMS.com

What's pushing teams away

  • Aged technical baseline — the vendor site lists system requirements of 'Internet Explorer 6.0 or compatible browser', a strong signal the product has not modernised, which scares off teams expecting current browser support and security posture.
  • Tiny public footprint — virtually no third-party reviews on G2, Capterra, GetApp, or Software Advice, making it hard for buyers to validate the product or compare against alternatives.
  • No documented public API, no developer portal, and no published rate-limit or authentication reference — integration-minded teams move to platforms with modern API surfaces.
  • Marketing channel mix references 'fax' as a primary outbound channel, indicating the product reflects late-1990s/early-2000s assumptions about sales workflows rather than current digital channels.
  • No published pricing tiers, customer count, or vendor company information makes long-term vendor risk hard to assess — buyers default to better-documented competitors.

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 myCRMS.com objects map to Freshsales

Each row shows how a myCRMS.com 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.

myCRMS.com

Contact

maps to

Freshsales

Lead or Contact (split required)

1:many
Fully supported

myCRMS.com contact records with a clear buying qualification status (from a sales_ready flag or equivalent field) map to Freshsales Contact tied to an Account. Contacts without a buying qualification status or with an unqualified stage map to Freshsales Lead. We determine the split criterion during the pre-migration audit based on which fields myCRMS.com exposes for qualification. Any original qualification status is preserved in a custom field for audit and reporting in Freshsales.

myCRMS.com

Company

maps to

Freshsales

Account

1:1
Fully supported

myCRMS.com company records map directly to Freshsales Account. The company name becomes Account Name, and any domain or website field becomes the Account Website field. Account is created before any Contact or Lead import so that the lookup relationship is satisfied at the moment of insert. We use Account Name as the dedupe key during import to prevent duplicate Account creation.

myCRMS.com

Deal

maps to

Freshsales

Deal

1:1
Fully supported

myCRMS.com pipeline deals map to Freshsales Deal records. The deal stage name from myCRMS.com maps to Freshsales Deal Stage, and any pipeline identifier maps to a Freshsales Deal pipeline that we configure before migration. Closed-won and closed-lost amounts, close dates, and owner assignments transfer directly. Custom deal fields migrate to Freshsales custom Deal fields created during the pre-migration schema phase.

myCRMS.com

Deal Stage

maps to

Freshsales

Deal Stage

lossy
Fully supported

Each deal stage from myCRMS.com becomes a Freshsales Deal Stage within the configured pipeline. Stage ordering and probability values transfer where available. Freshsales requires stages to be configured as a named list in Admin settings before deals can be imported; we configure this before any Deal records are loaded.

myCRMS.com

Activity: Calls

maps to

Freshsales

Calls (via Freshsales Activity module)

1:1
Fully supported

myCRMS.com call logs migrate to Freshsales as call activity records linked to the parent Contact, Lead, Account, or Deal. Call duration, disposition, timestamp, and owner assignment transfer where the export exposes those fields. Freshsales call activities appear in the Activity Timeline of the linked record.

myCRMS.com

Activity: Emails

maps to

Freshsales

Emails (via Freshsales Activity module)

1:1
Fully supported

myCRMS.com email logs migrate to Freshsales as email activity records linked to the parent Contact, Lead, Account, or Deal. Email subject, body content, sender, recipient, and timestamp transfer where the export exposes those fields. Freshsales email tracking features activate on the Growth plan and above; emails import as historical activity regardless of plan.

myCRMS.com

Activity: Tasks and Notes

maps to

Freshsales

Tasks

1:1
Fully supported

myCRMS.com tasks and notes migrate to Freshsales Task records linked to the parent Contact, Lead, Account, or Deal. Task status, priority, due date, and owner assignment transfer. Note content migrates as the Task description field, preserving the original timestamp. We resolve owner assignments by email match against Freshsales User records.

myCRMS.com

Custom Field

maps to

Freshsales

Custom Field

lossy
Fully supported

myCRMS.com custom fields on Contact, Company, and Deal objects migrate to Freshsales custom fields of matching data type. We discover the full custom field schema during the pre-migration audit (field name, type, picklist values if applicable), pre-create each custom field in Freshsales before any data loads, and then import data with the custom field mappings resolved. Text, number, date, picklist, and boolean field types are supported; multi-select picklists map to Freshsales multi-select fields.

myCRMS.com

Owner

maps to

Freshsales

User

1:1
Fully supported

myCRMS.com record owners map to Freshsales User records by email match. We extract every distinct owner referenced on Contact, Company, Deal, and activity records and match by email against the Freshsales User table. Owners without a matching Freshsales User go to a reconciliation queue for the customer's admin to provision before record import resumes.

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.

myCRMS.com logo

myCRMS.com gotchas

High

Vendor site references IE 6.0 — product likely not modernised

High

No public API or developer portal

Medium

No third-party review corpus for diligence

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

  • myCRMS.com export capabilities are minimally documented

    myCRMS.com has limited public API documentation, which means we may encounter proprietary export formats, incomplete field coverage in exports, or missing timestamps on activity records during the pre-migration audit. We handle this by running a discovery extraction first, validating record counts and field coverage, and flagging any missing fields before committing to the migration scope. If the export cannot produce activity history in a structured format, we limit the migration to Contacts, Companies, and Deals only and note the limitation in the scope document.

  • Freshsales field validation rules can reject imported records

    Freshsales enforces field-level validation on required fields, picklist whitelists, and data formats that may not match the data in myCRMS.com. A common example is phone number formatting: if myCRMS.com stores phone numbers without country codes and Freshsales requires them, records will be rejected on import. We address this during the transform phase by standardizing field formats (phone numbers, dates, email addresses) before loading, and we coordinate with the customer's Freshsales admin to temporarily disable or extend validation rules if bulk imports require it.

  • Smart Lists do not migrate to Freshsales filtered views

    myCRMS.com Smart Lists for contact segmentation are a query-layer feature that stores filter logic, not data. Freshsales filtered views and saved views are configured individually within the CRM and do not accept Smart List definitions as imports. We deliver a written inventory of every active Smart List in myCRMS.com with its filter criteria (field, operator, value) so the customer's admin can rebuild equivalent filtered views in Freshsales. This inventory is part of the standard migration handoff package.

  • Lead conversion logic must be defined before migration

    Freshsales treats Leads (unqualified prospects) and Contacts (qualified people tied to Accounts) as separate objects with an explicit conversion action. If the migration imports all myCRMS.com contacts as Freshsales Contacts without a corresponding Account, those Contacts will be orphaned. We resolve this by defining the qualification split rule during scoping (which contacts become Leads, which become Contacts with Accounts) before any data is loaded, and we document the split logic in the migration scope.

Migration approach

Six steps for a successful myCRMS.com to Freshsales data migration

  1. Discovery and Freshsales plan selection

    We audit the myCRMS.com portal for record counts across contacts, companies, and deals; identify custom field schemas on each object; assess whether the export exposes activity history (calls, emails, tasks) and owner assignments; and review any Smart Lists in use. We pair this with a Freshsales plan recommendation based on the customer's team size and required features: Free (up to 3 users) for basic contact and account management, Growth ($9/user) for built-in phone and Freddy AI, Pro ($39/user) for multiple pipelines and advanced automation, or Enterprise ($59/user) for custom objects and territory management.

  2. Schema design and custom field pre-creation

    We design the destination Freshsales schema before any data loads. This includes creating custom fields on the Contact, Account, and Deal modules to receive myCRMS.com custom field data; configuring Deal pipeline stages to match the myCRMS.com deal stages; and setting up the Lead-Contact split rule based on the qualification criteria discovered in scoping. Schema configuration is validated in Freshsales Admin settings before the production migration begins.

  3. Data export in dependency order

    We extract data from myCRMS.com in dependency order: companies first (so that Account records exist for Contact and Deal lookups), then contacts and leads with AccountId resolved, then deals with AccountId and OwnerId resolved, then activity history (calls, emails, tasks) with parent-record references resolved. Each extraction produces a row-count report that we reconcile against the myCRMS.com record counts before proceeding.

  4. Transform and field mapping

    We transform the extracted data to match Freshsales field types and validation requirements. Phone numbers are standardized to E.164 format where required. Dates are converted to Freshsales-accepted formats. Owner email addresses are mapped to Freshsales User IDs. Any field that maps to a Freshsales picklist is validated against the allowed values. We apply data cleansing to remove duplicate records (identified by email deduplication on contacts) and to populate required fields with defaults where myCRMS.com data is absent.

  5. Production migration and reconciliation

    We run the migration into the live Freshsales account in phase order: Accounts (from myCRMS.com companies), then Contacts and Leads (with AccountId lookups resolved), then Deals (with AccountId and OwnerId resolved), then activity records. Each phase emits a row-count reconciliation report. We spot-check 25-50 records per object against the myCRMS.com source and resolve any discrepancies before declaring the migration complete.

  6. Cutover, validation, and Smart List handoff

    We freeze myCRMS.com writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the Smart List inventory document to the customer's admin team for rebuild as Freshsales filtered views. We support a one-week hypercare window where we resolve any data quality issues reported by the sales team. We do not rebuild Smart Lists or any automation logic inside the migration scope.

Platform deep dives

Context on both ends of the pair

myCRMS.com logo

myCRMS.com

Source

Strengths

  • Browser-only delivery with no client install.
  • Sales pipeline, opportunity tracking, and multi-period forecasting included in core product.
  • Marketing automation across email, letter, and fax channels bundled in.
  • Month-to-month cancellation (one month's notice) lowers commitment risk.
  • Free trial available without annual commitment.

Weaknesses

  • Vendor site lists IE 6.0 as a supported browser — suggests the product has not modernised.
  • Virtually no public third-party reviews on G2, Capterra, or other major directories.
  • No documented public API or developer portal.
  • Marketing copy references fax as an outbound channel, indicating outdated workflow assumptions.
  • No published pricing tiers, customer count, or vendor company information.
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?

Moderate CRM migration. 1 of 8 objects need a manual workaround.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across myCRMS.com and Freshsales.

  • Object compatibility

    D

    1 of 8 objects need a manual workaround.

  • 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

    myCRMS.com: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your myCRMS.com 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 myCRMS.com to Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between one and three weeks for accounts under 10,000 Contacts and 2,000 Deals with no complex custom field schemas and limited activity history. Migrations with significant custom field schemas, dirty data requiring pre-load cleansing, or large activity histories (over 100,000 engagement records) move to three to six weeks because of the transform and Freshsales validation rule remediation work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from myCRMS.com.
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