Migrate from SuiteCRM to Microsoft Dynamics 365 Sales

SuiteCRM Accounts map directly to Dynamics 365 Account. The Account Name, Industry, Website, and Billing Address fields migrate as typed fields. Account is created first in all import passes so that the AccountId lookup is satisfied for any child Contact or Opportunity records. We use the Account Name as the dedupe key during import to prevent duplicate Account creation.

SuiteCRM Contacts map to Dynamics 365 Contact with an AccountId lookup resolved to the parent Account created in the Accounts pass. Primary fields (Full Name, Email, Phone, Job Title, Mailing Address) migrate as typed fields. Any custom fields added via SuiteCRM Studio are created as equivalent custom fields in Dynamics 365 before the Contact import begins. Contacts without a resolvable parent Account are held in a reconciliation queue for admin review; Dynamics 365 requires Contacts to be linked to an Account unless the customer has opted for a Lead-only migration strategy.

SuiteCRM Leads are a standalone module with status and source fields but no native Convert action equivalent to Dynamics 365. We offer two strategies: (a) pass-through maps all SuiteCRM Leads to Dynamics 365 Leads preserving lead status, source, and rating; (b) Account-attached maps Leads to Contacts under the matched Account for organisations that used Leads as a secondary Contact type. The strategy is decided during scoping based on the customer's sales process.

SuiteCRM Opportunities map to Dynamics 365 Opportunity. The Opportunity Name, Amount, Close Date, and Sales Stage migrate as typed fields. SuiteCRM stage values are mapped to Microsoft Dynamics 365 Sales Process stage values defined during the schema configuration pass. The parent AccountId and OwnerId (User) are resolved before Opportunity import. Probability is mapped from SuiteCRM's probability percentage field if present.

SuiteCRM Products map to Dynamics 365 Product2 records. Product Name, Part Number (SKU), and Description migrate. A Standard Price Book entry is created during import so that the Product can be added to Opportunity line items. If SuiteCRM's product catalogue uses a custom taxonomy (categories, types), we create the equivalent Category structure in Dynamics 365 before product import.

SuiteCRM Quotes map to Dynamics 365 Quote, linked to the parent Opportunity resolved from the Quote-Opportunity relationship. Line items are mapped to QuoteLineItem records referencing the Product2 records imported in the Products pass. Quote status (Draft, Active, Revised, Accepted, Closed Won, Closed Lost) maps to the Dynamics 365 Quote status values.

SuiteCRM Contracts have start date, end date, renewal status, and terms but no native accounting ledger. We map Contract records to a custom Contract__c object in Dynamics 365 with fields for contract terms, start/end dates, and a renewal date alert. If the customer uses Microsoft Dynamics 365 Sales Enterprise or above with integrated finance modules, Contracts are linked to the parent Account.

SuiteCRM Cases (the Bugs module) map to Dynamics 365 Case with Subject, Description, Priority, and Status preserved. Case origin and type fields map to Dynamics 365 Case Origin and Case Type. Cases are linked to the parent Contact or Account where the relationship exists in SuiteCRM. Case activities and notes are migrated as separate Activity and Note records linked to the Case.

SuiteCRM Campaigns with target lists map to Dynamics 365 Campaign. Campaign Name, Status, Type, and Budgeted Cost migrate as typed fields. The target list memberships (Contacts and Leads assigned to the campaign) migrate as CampaignMember records linked to the Campaign. Email response activity (opens, clicks) from SuiteCRM campaign tracking is extracted as activity records.

SuiteCRM call activities map to Dynamics 365 Task with TaskSubtype = Call and CallDurationInSeconds preserved in a custom field. Meeting activities map to Event with StartDateTime, EndDateTime, and Location preserved. Email activities map to Task (activity timeline entry) with EmailMessage content linked. Tasks map to Task with Status and ActivityDate preserved. We resolve the WhoId (Contact or Lead) and WhatId (Account or Opportunity) for each activity before insert.

SuiteCRM Documents store files on the server filesystem with a database record holding metadata. We extract the file blobs from the SuiteCRM upload directory, preserving the original filename and folder structure, upload them to a SharePoint library connected to the Dynamics 365 environment, and create Document Location records that link the SharePoint files back to the target CRM records (Account, Contact, Opportunity, Case). File permission issues are a known migration risk; we validate read access and checksum all files during extraction.

SuiteCRM Users referenced as record owners on Accounts, Contacts, Opportunities, and Activities are resolved by email match against the destination Dynamics 365 User table. Owners without a matching User record are placed in a reconciliation queue for the customer's admin to provision before the relevant import pass resumes. Historical Owner assignments are preserved by mapping the owner email to the new User record.