Migrate from SuperOffice CRM to Microsoft Dynamics 365 Sales

SuperOffice Company records map directly to Dynamics 365 Account. The Company name becomes Account Name, the business registry number (if stored in a custom field) becomes DUNS Number or a custom field, and the primary address maps to the Address1 composite. Company is the first object migrated so that Account records exist before Contact import resolves the parent customerid lookup. We use Company name as the dedupe key during import to prevent duplicate Account creation.

SuperOffice Contact records map to Dynamics 365 Contact with the parent Account resolved via the SuperOffice associate table. Email, phone, title, department, and address fields migrate directly. Custom fields on Contact transfer to equivalent custom fields in Dynamics. If the destination org uses the Lead object for pre-qualified records, we apply a qualification rule during scoping (e.g., Contacts without an active Sale become Leads; Contacts with a Won or active Sale become Contacts attached to the Account).

SuperOffice Sale records map to Dynamics 365 Opportunity. The Sale amount maps to Amount, the sale stage (from the Salestype link table) maps to the Opportunity StageName within the configured Sales Process, and the Sale currency maps to TransactionCurrencyId. Closed-won and closed-lost dates migrate to CloseDate and a custom Closed_Lost_Date__c field. We configure Opportunity Record Types and Sales Processes in Dynamics before migration so that stage values are whitelisted per sale type.

SuperOffice Quotes linked to Sales migrate to Dynamics 365 Quote records. The Quote header fields (validity period, payment terms, delivery terms) map to the corresponding Dynamics Quote fields. Each QuoteAlternative becomes a set of QuoteLineItem records. Secondary and tertiary QuoteAlternatives are serialized as a JSON blob in a custom field alt_proposal_data__c on the Quote so that the admin can reference the unselected proposal versions post-migration.

Each SuperOffice QuoteAlternative maps to a set of Dynamics 365 QuoteLineItem records. Line item fields (product, quantity, unit price, discount percentage, line total) migrate directly. Discount and earning tracking at the Alternative level in SuperOffice maps to a custom field on QuoteLineItem. If the Quote has no alternatives (single-version proposals), migration is a direct 1:1 line-item map without the JSON serialization step.

SuperOffice Project records have no native equivalent in Microsoft Dynamics 365 Sales . If the destination org includes Project Service Automation ($110/user/mo addon), we map to the native msdyn_project entity with its Project Team, Project Tasks, and Bookable Resource associations. If Project Service Automation is not licensed, we create a custom crt_project__c entity with the relevant fields and note the limitation in the handoff documentation. Project-type and project-status links from SuperOffice's ProjType and ProjStatus tables store as custom fields on the project record.

SuperOffice Activities map to Dynamics 365 Task (for calls and tasks) and Event (for appointments/meetings). The activity type (call, task, appointment) is encoded in TaskSubtype and Subject prefix. Duration, completion status, and timestamps migrate directly. We link each Activity to the parent Contact or Company via the WhatId (for Contact/Company-linked activities) or WhatId (for Sale- or Project-linked activities). Activity associations require a lookup resolution pass because SuperOffice's associate table allows multi-object links that Dynamics does not natively support.

SuperOffice Selections are dynamic named lists of Contacts, Companies, or Sales. Dynamics 365 has no native equivalent to dynamic lists. We export the current membership of each Selection as tagged records with a custom field selection_name__c holding the selection title. Post-migration, the admin rebuilds the dynamic logic as a Power Automate flow or a saved view with the equivalent filter criteria. Selection counts and names are delivered in the handoff spreadsheet for reference.

SuperOffice documents stored in the document archive migrate as binary blobs with metadata (filename, created date, author, file type, record association). Microsoft Dynamics 365 Sales natively integrates with SharePoint Online for document management. We export the document archive, upload to the configured SharePoint document library, and link via the regardingobjectid on SharePoint document location records. Legacy .doc/.xls/.ppt files are migrated but flagged for admin review since Graph API editing limitations apply.

SuperOffice userDefined table fields on Contact, Company, Sale, and Project migrate to Dynamics 365 custom fields of equivalent type (text, integer, decimal, date, picklist, checkbox). Dropdown lists require the destination picklist values to be pre-created in Dynamics before migration; we include the value set in the pre-migration schema checklist. Custom fields are deployed to the Sandbox first for type validation before production import.

SuperOffice Tags applied across Contact, Company, Sale, and Project objects migrate to a custom crt_tags__c multi-select picklist field on each object. Tag names with special characters are sanitized to Dynamics-allowed picklist value formats. The admin recreates the tag vocabulary in Dynamics before production migration begins.

SuperOffice Users (Associates) map to Dynamics 365 User records by email address. We extract the associate table, resolve each SuperOffice user to a Dynamics User by email match, and flag any SuperOffice user without a matching Dynamics User for admin provisioning before migration. Role structures (module-level access in SuperOffice) map to Dynamics security roles, though the permission model differs significantly and requires a role-mapping exercise during discovery.