Migrate from Inception to Microsoft Dynamics 365 Sales

Direct map for all standard contact fields. Inception contacts where lifecycle stage equals Customer or Evangelist land as Dynamics 365 Contacts. All other lifecycle stages route to Lead (see split rule). Inception contacts without an organization get attached to a default placeholder Account; FlitStack surfaces this before migration for your team to resolve.

Inception contacts where lifecycle_stage is Lead, MQL, or SQL (but not Customer or Evangelist) split to Dynamics 365 Lead. The original Inception lifecycle stage value is preserved in Lifecycle_Stage__c on the Lead record. FlitStack generates a split map during the pre-migration schema analysis phase so you can review which records land where before data moves.

Direct map: Inception Organization becomes Dynamics 365 Account. Parent-child organization hierarchies in Inception map to ParentAccountId on the Account record; FlitStack flags circular parent references before migration so they can be resolved manually. Multi-company associations on Inception contacts collapse to a primary AccountId plus Account Contact Relationships in Dynamics.

Inception Deal maps to Dynamics 365 Opportunity. The deal's pipeline field becomes the Opportunity's recordtypeid — FlitStack creates one Dynamics 365 record type per Inception pipeline before migration so the mapping is valid at insert time. Stage names map value-by-value to the pick-list defined on each record type's business process flow.

Inception pipeline is not a standalone object — it is a property on Deal. Each unique Inception pipeline value generates one Dynamics 365 Sales Process (record type) so stage pick-list values are scoped correctly per pipeline. FlitStack delivers a record-type setup plan as part of the pre-migration package so your Dynamics admin can create these before data lands.

Inception deal stage is a free-form text property on Deal. Each stage name maps to a named Opportunity Stage value on the relevant record type. Probability, forecast category, and stage-entered timestamp are preserved as custom fields. If Inception stage names differ from Dynamics defaults, FlitStack creates the target stage values during schema setup.

Dynamics 365 has no native lifecycle stage equivalent. FlitStack creates a custom pick-list field (Lifecycle_Stage__c) on both Lead and Contact with the exact Inception stage values. A second custom field (Lifecycle_Stage_Date__c) stores the last stage-changed timestamp for reporting continuity. Both fields are created during the pre-migration schema phase.

Inception call records (subject, direction, duration, notes) map to Dynamics 365 PhoneCall activity. Original start timestamp, owner, and contact/lead parent links are preserved. Call direction (inbound/outbound) maps to DirectionCode on the PhoneCall. All call metadata such as disposition code, result, and participants are also mapped to the corresponding PhoneCall entity fields to preserve full interaction context for future reference.

Inception email engagement records migrate as Dynamics 365 Email (activity) with subject, body, and timestamp. Original sender, recipient, and parent-record links are preserved. FlitStack strips HTML wrapper formatting that may not render in Dynamics activity timelines. Attachments embedded in the email body are re-linked as Dynamics 365 attachments; the email's thread ID is stored for threading continuity.

Inception meeting records with subject, start/end time, location, and notes map to Dynamics 365 Appointment (Event) records. Original start/end timestamps and owner are preserved. Required/optional attendee status is not native in Inception; FlitStack flags this for manual review in Dynamics.

Inception notes migrate as Dynamics 365 Note (annotation) records attached to the parent Contact, Lead, Account, or Opportunity. Rich-text formatting is preserved where Dynamics character limits allow; long-form notes get a custom Long_Note__c field to prevent truncation. Links to related records, tags, and sentiment scores are migrated to custom fields to maintain contextual metadata beyond plain text.

Inception Enterprise custom objects map 1:1 to Dynamics 365 custom tables. FlitStack reads the Inception API schema for each custom object, creates the corresponding Dynamics table with the same field types (text, number, pick-list, lookup), and maps relationship fields as lookup columns. If Inception uses N:N relationships, FlitStack creates junction tables in Dynamics.

Inception users (owner field on contacts, deals, activities) resolve by email match against the Dynamics 365 SystemUser table. Matched users populate OwnerId on migrated records. Inception users with no Dynamics account are flagged before migration; your team assigns them to a fallback owner or creates their Dynamics user accounts before the migration run.

Inception file attachments on contacts, organizations, and deals are re-uploaded as Dynamics 365 Note records with the file attached. Files exceeding Dynamics attachment size limits (25 MB per file) are stored in a linked SharePoint document library; FlitStack creates the SharePoint structure and attaches links on the parent CRM record.