Migrate from Moskit to Microsoft Dynamics 365 Sales

Moskit Contact records (pessoa-level, storing name, email, phone, custom properties) map directly to Dynamics 365 Contact. We extract all standard fields plus any custom properties discovered per object via schema queries run during extraction. The Contact's primary email address becomes the EmailAddress1 field used as the dedupe key on import. We preserve Brazilian Portuguese field labels as custom field display names and deliver a Portuguese-to-English field label glossary so Dynamics admins can navigate without BR-language fluency.

Moskit Company records (organização-level, linked to Contacts via a foreign key relationship) map to Dynamics 365 Account. The Company domain, address, industry classification, and custom fields all migrate to equivalent Account fields. Account is imported before Contact so that AccountId is resolved at the moment of Contact insert, satisfying the required Lookup relationship.

Moskit Deals (Negócios) map to Dynamics 365 Opportunity. The dealstage property maps to StageName, and the Moskit pipeline assignment maps to a Microsoft Dynamics 365 Sales Process or Record Type configured before migration. Deal monetary value migrates to Amount; closed-won and closed-lost dates migrate to CloseDate and a custom closed_reason__c field. Custom deal properties discovered during schema extraction migrate as custom Opportunity fields.

Moskit pipelines contain custom-named stages with stage-order sequencing. We map stage names and order to Microsoft Dynamics 365 Sales Process stage values, and migrate stage-level probability percentages to StageProbability. If Moskit uses a stage naming convention in Portuguese, we preserve the Portuguese name in a custom field for audit and configure an English-language StageName that aligns with the customer's chosen Microsoft Dynamics 365 Sales Process.

Moskit Activities (Atividades) represent tasks, calls, meetings, and notes linked to Deals or Contacts. Activity type labels in Portuguese (e.g., Tarefa, Ligação, Reunião) map to Dynamics 365 Task and Event objects based on activity type. Timestamps, owners, descriptions, and linked record references migrate. Activity type labels are translated in the field label glossary. The activity's linked Deal or Contact reference is resolved at migration time by querying the destination record's Dynamics ID.

Moskit Projects are deal-centric and spawned from Deal records. Microsoft Dynamics 365 Sales has no native standalone Project object. We migrate Projects as a custom Dataverse entity with a lookup to Opportunity. The Project's deal reference is resolved in two passes: first importing Deals (storing source Moskit deal ID in a custom field), then Projects with the deal reference remapped to the corresponding destination Opportunity ID. Task-level detail within Projects migrates as custom Project Task records on the same custom entity.

Moskit allows custom fields on Contacts, Companies, Deals, and Activities. We query each object type individually during schema discovery to enumerate its custom field definitions (Moskit does not expose a bulk custom-field enumeration endpoint). Each custom field is type-mapped to the closest Dynamics 365 field type (text to Single Line of Text, picklist to Option Set, date to Date Only, number to Whole Number or Decimal). Custom fields are deployed to the destination Dynamics 365 environment via Dataverse API before any record data is loaded.

Moskit User records (name, email, role, active/inactive status) are exported and matched to Dynamics 365 User records by email address. Inactive Moskit users are included with an IsActive flag set to false in a custom field so they can be provisioned correctly in Dynamics 365. Any Moskit Owner without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Moskit's WhatsApp Business sync stores conversation references linked to Contact records, but the actual message content lives in WhatsApp's infrastructure. We extract conversation metadata (timestamps, participant count, message count, conversation status) as Note records linked to the Contact in Dynamics 365. We flag this gap explicitly in the scoping report so the customer can decide whether to export WhatsApp data separately from WhatsApp Business Manager. Full message history does not migrate.