Migrate from MarketSharp to Microsoft Dynamics 365 Sales

MarketSharp leads map directly to D365 leads with original creation timestamp and owner preserved. Address and phone fields align with D365 lead field names. Lead source tracking data migrates to D365's leadsource field with value-by-value mapping where picklist values differ.

Individual contact records map to D365 contacts. MarketSharp's company-on-contact collapses to an AccountId lookup — the primary company becomes the primary account, and additional company associations create Account Contact Relationships. Original contact creation date is preserved as a custom field since D365's CreatedOn reflects migration time.

MarketSharp company records map directly to D365 accounts. The parent‑company hierarchy translates to the ParentAccountId lookup, enabling the same organizational structure in Dynamics 365. However, any circular parent‑account references must be identified and resolved before migration, because D365 does not permit circular chains in the parent‑account relationship, which would cause import failures or data integrity issues.

MarketSharp deal records are transformed into D365 opportunities, with the deal amount moving to the estimatedvalue field, pipeline stage mapping to the opportunity stage via value‑by‑value translation, and the close date becoming estimatedclosedate. The owner is resolved by matching the MarketSharp owner’s email to a corresponding D365 user account, ensuring proper record assignment after migration.

Scheduled appointments in MarketSharp are imported as D365 appointments, preserving the original start time, end time, subject, location, and attendee details. The regarding object is linked to the corresponding lead, contact, account, or opportunity based on MarketSharp’s reference type, and the owner is assigned by matching the email address to a D365 user record.

MarketSharp's contractor-specific project entity has no native D365 equivalent — D365 Sales lacks a built-in project management entity. FlitStack creates a custom Project table in Dataverse and migrates project records with fields for project name, budget, status, timeline, and linked deal or contact as custom fields. Custom forms and views must be configured post-migration to surface the data in the D365 UI.

All MarketSharp custom fields migrate to D365 as custom fields using the new_ API name prefix. Option-set fields require either matching integer values or global option sets in D365 to prevent silent default-to-first-value errors during import. Field-level security is configured per custom field to control visibility across security roles.

File attachments on leads, contacts, accounts, deals, and appointments transfer to D365 notes with file attachments. File content, original filename, and MIME type are preserved. D365 enforces a 25MB per-file limit; larger attachments are flagged for manual retrieval.

MarketSharp users are matched to D365 users by email address. When no matching D365 user exists, FlitStack generates an exception report that lists the unmatched users and the number of records they own. The organization must then either provision a corresponding D365 user account before migration or assign those records to a designated fallback owner to ensure every record has a valid owner after the migration runs.

Call logs become phonecall activities, email history becomes email activities, and notes become note records in D365. Each activity preserves its original timestamp, owner, and parent record link (contact, account, or opportunity). Activity type determination is based on MarketSharp's engagement type field.

MarketSharp's lead-source picklist values are mapped value-by-value to D365's leadsource option set. If MarketSharp uses custom source values not present in D365, FlitStack creates a custom lead source field and maps the values there, notifying the admin of the custom field creation.

Products and services defined in MarketSharp migrate to the D365 product catalog, preserving product name, SKU, unit price, and description. Products must be created before quote line items reference them, so product migration runs before quote migration in the sequence.

Sales quotes created in MarketSharp are imported as D365 quotes, with each quote’s line items transferred to quotedetail records. Pricing, quantities, discounts, and associated product references map directly to D365 fields, and the quote status translates through a value‑by‑value mapping of MarketSharp status codes to D365’s statuscode option set, ensuring the sales pipeline reflects the same deal progress after migration.

MarketSharp tasks and to‑do items are migrated as D365 tasks, preserving the subject, due date, priority, status, and owner assignment. Open tasks retain an open state, while completed tasks are imported with their original completion timestamp and the state set to completed, allowing your team to maintain a full history of work performed after the migration.