Migrate from MiniCRM to Microsoft Dynamics 365 Sales

MiniCRM Cards are the primary record container and may simultaneously hold Contact fields (name, email, phone), Company fields (company name, address), Deal fields (deal value, pipeline stage), custom fields, and task associations. We decompose each Card at migration time into a Contact record (the card's contact fields), an Account record (the card's company fields), and an Opportunity record (the card's deal fields), then resolve the AccountId and OwnerId foreign keys on Contact and Opportunity before insert. The original Card ID is preserved in a custom field minicrm_card_id__c for audit reconciliation.

Contact-level fields including full name, email address, phone number, and physical address migrate directly to the Microsoft Dynamics 365 Sales Contact schema. The minicrm_contact_id is stored as a custom attribute for lookup resolution during the Card decomposition phase. If a Card contains only contact data with no associated Company or Deal, it migrates as a standalone Contact record without a parent Account.

MiniCRM Company records map to Microsoft Dynamics 365 Sales Account. We resolve Company name as Account Name, physical address fields map to Address composite fields, and any additional company properties map to custom Account attributes. If a Company appears on multiple Cards, we create one Account and link all decomposed Contact records to it. Account is created before the Contact decomposition phase so that AccountId is available at Contact insert time.

MiniCRM Deals (called Interests) map to Microsoft Dynamics 365 Sales Opportunity. Pipeline stage names from MiniCRM are mapped to a Microsoft Dynamics 365 Sales Process (Record Type) configured before migration. Deal value, close date, and deal owner migrate to EstimatedValue, CloseDate, and OwnerId on Opportunity. Closed-won and closed-lost reasons in MiniCRM map to custom Opportunity fields. We resolve the parent AccountId from the Card's associated Company during the decomposition phase.

MiniCRM Tasks linked to Cards migrate to Microsoft Dynamics 365 Sales Task records. Subject, Description, Due Date (ScheduledEnd), Status, Priority, and Assigned User migrate directly. Task recurrence patterns and reminder settings are preserved as custom fields because Dynamics 365 Task recurrence is modeled differently. We resolve the Regarding (regardingobjectid) reference to the decomposed Contact or Opportunity record from the parent Card.

Free-text notes attached to MiniCRM Cards migrate as Microsoft Dynamics 365 Sales Annotation records (the standard note object on Dataverse). Note body migrates as the notetext attribute. We link each Annotation to the parent Contact or Opportunity via the objectid reference resolved from the source Card. Polish-language note content is preserved as-is without translation.

MiniCRM custom fields on Cards are detected during scoping and mapped to typed Dataverse custom attributes on the Contact entity. Text fields map to nvarchar, number fields to decimal or integer, date fields to datetime, and choice fields to option set. Choice field values require explicit mapping to the target option set labels. Custom attributes are pre-created in the Dynamics 365 environment before the Card decomposition migration phase begins.

MiniCRM User records (name, email, role) map to Microsoft Dynamics 365 Sales User records by email match. Role distinctions in MiniCRM may not map directly to Dynamics 365's security role model; we preserve the MiniCRM role name in a custom field minicrm_role__c for the customer's admin to assign appropriate Dynamics security roles post-migration. Users without an email match go to a reconciliation queue for manual provisioning.

MiniCRM automation rules (trigger/action sequences tied to card status changes, field fills, and deadlines) are server-side and not exposed through any documented export endpoint. We do not migrate them. We document every active automation rule during discovery — including trigger type, conditions, actions, and affected card statuses — and deliver a written inventory recommending equivalent Microsoft Dynamics 365 Sales Process stages, Power Automate triggers, or workflow steps for the customer's admin to rebuild.