Migrate from Aritic Sales CRM to Microsoft Dynamics 365 Sales

Aritic Contacts with a clear buyer lifecycle stage map to Dynamics 365 Contact attached to a primary Account. Unqualified inbound leads that have not been worked by a sales rep map to a Dynamics 365 Lead for the customer's admin to qualify and convert. We preserve Aritic's lifecycle stage as a custom field on both the Lead and Contact for audit and reporting continuity. Any Contact with multiple Aritic Company associations is flagged: the primary Company becomes the primary Account lookup, and secondary Company associations are written to a custom lookup field or held in a reconciliation note for the customer's admin to verify in Dynamics.

Aritic Company records map directly to Microsoft Dynamics 365 Sales Account. The Company domain becomes the Account Website field. We import Accounts first in every migration to establish the foreign-key relationship that Contacts, Deals, and Activities depend on. Account is the primary entity in Dynamics 365's data model, and creating it before any child record ensures that the AccountId lookup is satisfied at insert time, avoiding orphaned Contact and Opportunity records.

Aritic Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal stage names map to Dynamics Opportunity stage values via a custom mapping table we build during scoping. The Deal amount, close date, probability, and owner assign to the corresponding Opportunity fields. Aritic's multi-pipeline structure maps to Dynamics Opportunity Record Types and Sales Processes, which we configure in the destination org before migration begins. Closed-won and closed-lost reasons from Aritic custom fields map to Dynamics custom fields on Opportunity.

Each Aritic pipeline maps to a Dynamics 365 Opportunity Record Type with a corresponding Sales Process. The Sales Process defines the whitelisted stage values and probability percentages per pipeline. We build the Record Type and Sales Process in the Dynamics 365 org before migration so that Opportunity records land with the correct RecordTypeId already assigned. Stage ordering and win/loss criteria carry forward from Aritic; stage-level automation triggers are documented as a workflow gotcha for the customer's admin to rebuild in Dynamics 365.

Aritic's numeric lead score per Contact exports as a static value and maps to a custom integer field on the Dynamics 365 Lead or Contact record. The active scoring rule model (rules, weights, behavioral triggers) is not portable from Aritic. We provide a scoring-rule inventory sheet that enumerates each rule, its trigger condition, the fields it evaluates, and its score increment. A Dynamics admin can reconstruct these rules using Microsoft Dynamics 365 Sales ' native relationship analytics (Enterprise and Premium) or a third-party scoring tool. Each complex scoring rule typically takes 1-2 hours to rebuild.

Aritic invoice records (line items, totals, currency, payment status) migrate to a custom Invoice entity in Dynamics 365 or to Opportunity Product Line Items depending on the customer's use case. Multi-currency invoices require explicit currency code mapping to the Dynamics 365 transactioncurrencyid field. Payment status and invoice number migrate as custom fields. Invoice PDFs stored as URL-based attachments in Aritic are downloaded to the migration bundle and re-uploaded as Notes or SharePoint files linked to the Invoice record.

Aritic Activity records (call logs, email records, meeting notes, tasks) migrate to Microsoft Dynamics 365 Sales Task and Event objects. Calls map to Task with TaskSubtype=Call and CallDurationInSeconds preserved in a custom field. Meetings map to Event with StartDateTime, EndDateTime, and Location carried forward. Emails map to Task or EmailMessage depending on whether the customer wants them visible in the activity timeline. ActivityDate preserves the original Aritic timestamp for timeline ordering. Owner resolution by email match is required before Activity migration runs.

Aritic Owner records map to Microsoft Dynamics 365 Sales User records by email address. We run owner reconciliation before every migration: any Aritic Owner without a matching Dynamics User is placed in a reconciliation queue, and the customer's Dynamics admin provisions the missing User account before record migration resumes. Inactive Aritic users are preserved as inactive Users in Dynamics to maintain historical accuracy on Deals, Tasks, and Activities assigned to them.

Aritic custom fields on Contacts, Companies, and Deals are enumerated during the discovery phase. We map each custom field to a typed Dynamics 365 custom field (text, number, picklist, date, checkbox, etc.) and validate picklist values against the destination's picklist constraints. Formula-type custom fields from Aritic that depend on Aritic's expression syntax are documented as custom field notes for the customer's admin to implement as calculated fields or workflow formulas in Dynamics 365.

Aritic File Manager documents migrate to a SharePoint document library connected to the Dynamics 365 org or to Notes attached to the parent record. We detect URL-based attachments during the export scan: if the external URL is live, we download the file to the migration bundle; if the URL is expired or broken, we flag it as a broken link in the migration report for the customer to resolve. File organization in the migration bundle follows the Aritic structure organized by Contact and Deal ID.