CRM migration
Field-level mapping, validation, and rollback between myCRMS.com and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
myCRMS.com
Source
Freshsales
Destination
Compatibility
6 of 9
objects map 1:1 between myCRMS.com and Freshsales.
Complexity
CModerate
Timeline
1-3 weeks
Overview
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.
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 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
Freshsales
Lead or Contact (split required)
1:manymyCRMS.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
Freshsales
Account
1:1myCRMS.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
Freshsales
Deal
1:1myCRMS.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
Freshsales
Deal Stage
lossyEach 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
Freshsales
Calls (via Freshsales Activity module)
1:1myCRMS.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
Freshsales
Emails (via Freshsales Activity module)
1:1myCRMS.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
Freshsales
Tasks
1:1myCRMS.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
Freshsales
Custom Field
lossymyCRMS.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
Freshsales
User
1:1myCRMS.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.
| myCRMS.com | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact (split required)1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Deal Stage | Deal Stagelossy | Fully supported | |
| Activity: Calls | Calls (via Freshsales Activity module)1:1 | Fully supported | |
| Activity: Emails | Emails (via Freshsales Activity module)1:1 | Fully supported | |
| Activity: Tasks and Notes | Tasks1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Owner | User1: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.
myCRMS.com gotchas
Vendor site references IE 6.0 — product likely not modernised
No public API or developer portal
No third-party review corpus for diligence
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
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.
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.
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.
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.
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.
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
myCRMS.com
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across myCRMS.com and Freshsales.
Object compatibility
1 of 8 objects need a manual workaround.
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
myCRMS.com: Not publicly documented.
Data volume sensitivity
myCRMS.com 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 myCRMS.com to Freshsales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave myCRMS.com
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.