Migrate from Fergus to Microsoft Dynamics 365 Sales

Fergus clients map directly to Dynamics 365 Accounts. We preserve the new_pricingtier custom field to hold the Fergus pricing-tier name so your Dynamics admin can rebuild the tier as a price-list setup or leave it as a reference field on the Account record.

Fergus Contact records map directly to Dynamics Contacts with a 1:1 relationship, attached to the parent Account record. We preserve the original Fergus contact ID in the new_ferguscontactid custom field to maintain traceability throughout the migration and support delta-run de-duplication processes on subsequent data synchronizations.

Fergus sites have no native Dynamics 365 equivalent, so we create a child Account record under the primary client Account. The site name, full address fields (street, city, state, postcode, country), and new_sitetype custom field are migrated onto this child Account. Parent-child linking between the site Account and client Account is achieved using the Dynamics ParentAccountId relationship field.

Dynamics 365 Sales has no native job-card entity. We create a custom Job__c table in Dataverse with fields for name, description, new_jobstatus pick-list, new_scheduleddate, new_jobvalue, and a lookup to the parent Account and Site Account. This preserves the full job record without forcing it into the Opportunity object.

Fergus quotes map to Dynamics Opportunities. The Fergus quote status (draft, sent, accepted, declined, expired) becomes a new_quotestatus custom pick-list on the Opportunity record, mapped value-by-value to your Dynamics sales process stages. Quote total amount maps to the Opportunity EstimatedValue field, preserving financial data for pipeline reporting.

Fergus quote line items become Opportunity Products with standard Quantity, UnitPrice, and Description fields. The line item Description captures the Fergus product or service name. Each line item links back to the parent Opportunity via OpportunityId and optionally connects to the related Job__c record via a custom lookup field if a job-to-quote association exists in Fergus.

Fergus invoices with a 'paid' status map to Dynamics SalesOrder records in an invoiced state; unpaid invoices map to open Order records. We preserve the original paid status as a new_invoicestatus custom field on the SalesOrder so your Dynamics admin can verify reconciliation against Fergus records post-migration and confirm all payments transferred correctly.

Fergus pricing tiers are a named property on clients — they do not have a direct Dynamics equivalent. We migrate the tier name as a custom pick-list field (new_pricingtier) on Account with value-by-value mapping to the exact tier names in Fergus. Rebuild as price-list logic is a separate step for your Dynamics admin.

Fergus job phases are a list of stages on a job. We collapse them into Opportunity Product line items on the linked Opportunity with Description storing the phase name and Quantity = 1, UnitPrice = 0 or the phase value if charged. This preserves phase history without requiring a custom phase object.

Fergus file attachments on jobs, quotes, and clients are re-uploaded as Dynamics Notes with the file body stored in SharePoint or Dataverse file storage. File size limits per Dynamics apply; inline images in rich-text notes are downloaded and rehosted, then re-inserted into the new system with links preserved. The note rendering may differ slightly from Fergus's original formatting.

Fergus asset records tracking equipment and assets at a client site have no standard Dynamics equivalent. We create a custom Asset__c table in Dataverse with fields for asset name, new_assettype custom field for asset classification, new_location field as a lookup to the Site Account, and a link to the parent client Account for asset-to-account reporting and asset lifecycle management.

Fergus owner assignments are resolved by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration — your team either creates the Dynamics user first or assigns to a fallback owner. No record lands without a valid OwnerId.