Migrate from Fame Service to Microsoft Dynamics 365 Sales

Fame Service Contact maps directly to Dynamics 365 Contact. The primary organization from Fame Service resolves as AccountId on the Contact record. If Fame Service stores multiple organization associations, the primary organization becomes the AccountId lookup and secondary associations are stored in the Contact-Target field.

Fame Service Organization maps to Dynamics 365 Account. Parent-child hierarchies in Fame Service map to Account.ParentAccountId. If Fame Service stores multiple addresses per organization, the primary address maps to Address fields and additional addresses are stored as Account Addresses via the Dynamics 365 composite address model.

Fame Service Deal maps to Dynamics 365 Opportunity. The deal amount maps to Opportunity.Amount, close date to CloseDate, and deal name to Name. Owner resolution by email-match populates OwnerId. Pipeline and stage names require value mapping against Dynamics 365 Business Process Flow stages.

Fame Service stage names are mapped value-by-value to Dynamics 365 Opportunity StageName. Each Dynamics 365 stage belongs to a Business Process Flow; we map Fame Service stages to the appropriate BPF stage and record the stage Category (Default, Omitted, Lost, Won) from the Dynamics 365 stage-category model.

Fame Service owner IDs are resolved by email address against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration — your team either invites them to Dynamics 365 or assigns records to a fallback owner. This ensures no Opportunity or Contact lands without a valid OwnerId.

Fame Service email activities map to Dynamics 365 Email activity records. The regarding object links back to the originating Contact or Opportunity. Email body, subject, timestamps, and sender/recipient addresses are preserved. Large email attachments are downloaded and re-hosted in Dynamics 365 SharePoint integration or as Email Attachments.

Fame Service call logs map to Dynamics 365 PhoneCall activity records. Call direction (inbound/outbound), subject, duration, and call notes are preserved as PhoneCall fields. Owner and regarding object links to Contact or Opportunity carry over, maintaining the activity timeline in Dynamics 365.

Fame Service meeting records map to Dynamics 365 Appointment activities. Start time, end time, location, subject, and body are preserved as Appointment fields. If Fame Service stores attendee lists, we create corresponding ActivityParty records for each attendee linked to the Appointment, maintaining the full participant context in Dynamics 365.

Fame Service notes map to Dynamics 365 Annotation records. The annotation is linked to the regarding Contact, Account, or Opportunity. Rich-text formatting is preserved as HTML in Annotation.Notetext or stored as a file attachment if the formatting cannot be rendered in plain text.

Fame Service custom properties map to Dynamics 365 custom fields on the appropriate table. Text properties become Text fields, numbers become Decimal or Whole Number, dates become DateTime fields, and pick-lists become OptionSets. Dynamics 365 Sales Professional limits custom fields per table — Enterprise/Premium licenses support unlimited custom fields.

Fame Service product references attached to deals map as Opportunity Product records in Dynamics 365. Each Opportunity Product links to the parent Opportunity and a Product catalog record. Quantity, unit price, and discount fields carry over, updating the Opportunity Amount automatically.

Fame Service workflows and automations have no direct equivalent in Dynamics 365 — they require manual rebuild. We export Fame Service workflow definitions as a JSON reference document listing trigger conditions, actions, and field-update logic so your Dynamics 365 admin can replicate the automation in Power Automate or configure equivalent Business Process Flows.