Migrate from CRUMP CRM to Freshsales

CRUMP CRM Contacts are pulled from Dynamics 365 Contact entity via the web API. Freshsales distinguishes Leads (unqualified prospects) from Contacts (qualified). We evaluate the contact's statuscode, accountid, and any custom lifecycle or qualification fields to determine the split at migration time. Contacts with an associated Account and a closed or active business relationship become Freshsales Contacts; contacts without an Account or flagged as early-stage prospects become Leads. The original Dynamics 365 contact statuscode is preserved in a custom field dynamics_original_status__c for audit.

Dynamics 365 Account records map directly to Freshsales Account. The account name, website, industry, phone, address fields migrate 1:1. Parent-account hierarchy is preserved via the Freshsales Account parent_id field. Accounts must import before Contacts so that AccountId lookups resolve at Contact insert time.

Dynamics 365 Opportunity records (CRUMP CRM Deals) map to Freshsales Deal. The opportunitystage maps to Freshsales deal_stage_id, and pipeline assignment maps to Freshsales pipeline_id. We enumerate the source pipeline and stage values during audit and create matching Freshsales pipelines and stages before migration so that stage probabilities and names align. Close date, amount, probability, and owner migrate directly.

Projects live in the Dynamics 365 Project Management module—a distinct entity from CRM Opportunities. We export project records including project name, status, start and end dates, and assigned team members. In Freshsales, each project becomes a Deal with a custom field project_flag__c set to true and project_type__c carrying the original project status. Task-level detail below the project header is not migrated; we document the project task structure in a written handoff so the customer's admin can recreate it in a project management tool.

Helpdesk tickets export from Dynamics 365 as Cases with status, priority, title, description, and linked contact. We map ticket priority (low, normal, high, urgent) to Freshsales case_priority values, and ticket status to Freshsales case_status. Custom fields on tickets are enumerated during the audit phase and mapped to Freshsales custom case fields created before the import pass.

CRUMP CRM invoicing module exports invoice records with line items, totals, and payment status. Since Freshsales does not have a native invoicing object, we map invoice header data to the parent Deal as Deal Product entries, with invoice total recorded in a custom field original_invoice_total__c. The relationship to the originating Project or Deal is reconstructed from the Dynamics 365 export using the invoicing entity's regarding_objectid field.

Dynamics 365 tasks from the CRM, project, and helpdesk modules are deduplicated by activityid before export. Each task's regarding_objectid determines whether it links to a Contact, Account, Deal, or Case in Freshsales. Task status, priority, subject, description, due date, and owner migrate. Tasks are imported after the parent record (Contact, Account, Deal) exists in Freshsales to satisfy the lookup dependency.

Custom entities created on the Dynamics 365 instance are enumerated during the audit phase. Each custom entity's schema, field types, and relationships are documented individually since no two Dynamics 365 deployments share identical custom object structures. We create matching custom modules in Freshsales (Garden plan and above) before any data moves, including custom field creation and lookup relationship configuration. Custom objects that reference standard objects (Account, Contact, Deal) are imported last to ensure all parent records are present.

Dynamics 365 systemuser records are resolved by email against the Freshsales User table. We extract every distinct owner referenced on Contacts, Accounts, Deals, Tasks, and Cases and match by email. Users without a matching Freshsales User go to a reconciliation queue for the customer's admin to provision. Inactive source users are imported as inactive Freshsales Users to avoid orphaned ownership records.