Migrate from Sugar Sell to Microsoft Dynamics 365 Sales

Sugar Accounts map directly to Dynamics 365 Accounts. Standard fields (name, industry, website, phone, address) map field-by-field to AccountName, Industry, Website, Telephone, and the address composite fields. We use Account Name as the dedupe key during import. Account is created first so that the AccountId lookup is satisfied when Contacts are imported.

Sugar Contacts map to Dynamics 365 Contacts with AccountId as a required lookup. We resolve the AccountId by matching the parent Account record's name or external ID before Contact insert. Name fields (firstname, lastname), email, phone, title, and address composite fields migrate directly. Any custom fields on Contact are extracted from Sugar vardefs and pre-created as Dataverse columns before import.

Sugar Leads map directly to Dynamics 365 Leads. Lead status values (New, Assigned, In Progress, Converted, Recycled, Dead) map to standard LeadStatus values. Lead source and rating fields migrate directly. The original Lead score or rating from Sugar custom fields becomes a custom integer field on the Lead record.

Sugar Opportunities map to Dynamics 365 Opportunities with AccountId as a required lookup. Pipeline stage names from Sugar map to Microsoft Dynamics 365 Sales Process stage values. Probability, amount, date_closed, and description fields migrate directly. We configure the destination SalesProcess before migration so stage picklist values align with the source pipeline structure.

Sugar Call records map to Dynamics 365 Task with TaskSubtype set to Call. Duration, disposition, and related_to fields map to custom Task fields. The ContactId or other parent lookup is resolved at migration time by matching the related Contact's email or name. Activity timestamps are preserved to maintain the sales rep's timeline order.

Sugar Meeting records map to Dynamics 365 Event. Startdatetime, Enddatetime, Location, and Description migrate directly. Attendees are recreated as EventRelation records pointing to the related Contact, Lead, or Account. The original Sugar meeting subject becomes the Event subject.

Sugar Task records (non-call, non-meeting) map to Dynamics 365 Task with Status, Priority, ActivityDate, and Subject preserved. OwnerId is resolved by matching the Sugar assigned_user_id to a Dynamics 365 User by email. Tasks linked to parent records get the WhatId or WhoId set via lookup resolution at migration time.

Sugar Quotes map to Dynamics 365 Quotes at the Account level. Line items from Sugar's Product Bundle records map to QuoteDetails. Tax, discount, and total fields migrate field-by-field. Quote status values map to the Dynamics 365 QuoteStatus values. Note that Microsoft Dynamics 365 Sales Professional does not include Quotes by default; we recommend the Enterprise tier ($105/user) or a third-party CPQ ISV if quote management is a primary workflow.

Sugar Products map to Dynamics 365 Product2 records. ProductCode, Name, Description, and pricing fields migrate. Product Types and Manufacturers from Sugar become custom fields or category picklist values on Product2. We create the corresponding Pricebook and PricebookEntry records during migration.

Sugar Cases map to Dynamics 365 Cases with AccountId as a required lookup. Priority, status, resolution, and description fields migrate directly. Bug-specific fields from Sugar (Common in Advanced and Premier tiers) require custom fields on the Dynamics 365 Case entity. We pre-create the Case custom fields during schema preparation.

Sugar Studio custom fields require extraction from vardef PHP files or Module Loader package exports before migration. We parse the vardef entries to determine field type (varchar, int, decimal, enum, date, etc.), field label, and module assignment. We create equivalent Dataverse columns using the Dataverse column creation API, then import the data. SugarCRM Essentials customers who cannot use Module Loader require manual vardef export via file system access; we flag this during scoping.

Sugar Notes with text content migrate to Dynamics 365 Note records linked via RegardingObjectId to the parent Contact, Account, Lead, or Opportunity. File attachments are extracted from the Sugar file system or API response, re-uploaded to Dynamics 365 as Note or ActivityMimeAttachment records, and linked to the parent record. Large attachment handling (over 10 MB) requires chunking to stay within Dataverse file size limits.

SugarBPM workflow definitions are inventoried as named records with their trigger module, conditions, actions, and sequence ordering. We do not migrate SugarBPM as code because the cloud workflow action set differs from Power Automate's action library. We deliver a written inventory of every active SugarBPM definition with a trigger-condition-action map and a recommended Power Automate cloud flow equivalent. The customer's admin or a Microsoft partner rebuilds the workflows post-migration.

Sugar Users map to Dynamics 365 Users by email address. We extract every distinct owner_id referenced on migrated records and match against the destination User table. Users without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on most standard entities.