Migrate from DinamikCRM to Salesforce Sales Cloud

DinamikCRM Contact records map to Salesforce Contact. Standard fields (Name, Email, Phone, Title, Address) transfer directly. We use Email as the dedupe key during import and resolve the parent Account reference by matching DinamikCRM's Company link to the Salesforce Account created from the same Company record. Any DinamikCRM contact without a company link creates a bare Contact; the customer's admin reviews and links manually after migration.

DinamikCRM Company records map to Salesforce Account. The Account is created before Contact import so that AccountId is available at Contact insert time. We preserve the DinamikCRM industry classification, employee count, and annual revenue fields in matching custom fields on Account or in standard fields where names align. Website and address fields transfer directly.

DinamikCRM Lead records map directly to Salesforce Lead. Lead status values migrate into custom picklist fields or standard Salesforce Lead Status values based on a status-mapping table defined during scoping. Lead score and any source campaign tracking fields from DinamikCRM migrate to custom fields on Lead.

DinamikCRM Deal records map to Salesforce Opportunity. Deal value maps to Amount, deal stage maps to a Salesforce StageName within a Record Type we configure during schema design, and the DinamikCRM pipeline assignment maps to a Salesforce Sales Process or Record Type. Closed-Lost and Closed-Won dates preserve in custom fields if the destination org does not already capture these in standard fields.

Each DinamikCRM pipeline becomes a Salesforce Opportunity Record Type with a corresponding Sales Process. Pipeline stage names from DinamikCRM map to Salesforce StageName picklist values within that Sales Process. Stage probability percentages transfer to StageProbability on each stage definition. We configure this in the target org during the schema design step before any record migration begins.

DinamikCRM Activity records (calls, emails, meetings, tasks) split at migration time: calls and tasks map to Salesforce Task with TaskSubtype set appropriately; meetings and calendar events map to Salesforce Event. We preserve the original activity timestamp in ActivityDate and link to the parent Contact, Lead, or Account via WhoId and WhatId. Activity type metadata from DinamikCRM migrates to a custom ActivityType__c field on the destination task or event.

DinamikCRM Appointment records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee information from DinamikCRM generates EventRelation records linking the Event to the correct Contact or User in Salesforce. Any scheduling-specific fields in DinamikCRM (recurrence patterns, reminder settings) migrate to custom fields on Event and require admin review post-migration.

DinamikCRM Invoice records with line items map either to Salesforce OpportunityLineItem (if the destination org uses Salesforce quoting and has a Pricebook2 configured) or to a custom Invoice object we pre-create in Salesforce before migration. The customer's choice is confirmed during scoping based on whether Salesforce Sales Cloud's native quoting workflow is in use. Invoice totals, status, and payment terms transfer as custom fields.

DinamikCRM DESK module tickets map to Salesforce Case. Ticket priority and status migrate to Case Priority and Status within a DESK-specific Case Record Type we configure before migration. Conversation threads from DinamikCRM tickets migrate to Salesforce EmailMessage records linked to the Case. Assignee and team fields map to Case OwnerId resolved via the User email matching step.

DinamikCRM User records map to Salesforce User by email address. Every Contact, Deal, Activity, and DESK Ticket has an owner field that references a DinamikCRM User. We extract all distinct owners, match by email against the destination Salesforce org's User table, and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record migration resumes.

DinamikCRM file attachments linked to records export as file metadata (filename, URL reference, size, content type) and map to Salesforce ContentVersion and ContentDocument records. We create ContentDocumentLink records connecting each file to its parent Contact, Account, Opportunity, or Case. Whether actual binary file content migrates depends on DinamikCRM's file storage API access; if direct file download is unavailable, we flag this as a separate file migration task.

DinamikCRM's extensible module system means every account has a unique set of active custom modules. We run a schema discovery phase that enumerates every active custom module, its field definitions, data types, and inter-module relationships. We pre-create a matching Salesforce custom object for each custom module, including all custom fields with type-mapped Salesforce field types, before importing any data. Any DinamikCRM module-level business logic (filters, conditional displays, module-level automation) does not export and is flagged in the handoff document for declarative rebuild in Salesforce.

DinamikCRM Feedback entries (customer satisfaction, NPS-style responses) map to a Salesforce custom object (Feedback__c) pre-created during schema design. Feedback type, score, text content, and timestamp migrate to custom fields. If the customer intends to act on feedback within a support or success workflow, we recommend mapping to Case instead and confirm during scoping.

DinamikCRM tag assignments on records migrate to Salesforce multi-select picklist fields on the target object. Tags are extracted as a distinct list per object type, the customer selects a tag strategy during scoping (multi-select picklist per object or Salesforce Topics with TopicAssignment), and we apply the chosen strategy during the import phase.