Migrate from Aritic Sales CRM to Salesforce Sales Cloud

Aritic Contact records with lifecycle stage of prospect or unqualified map to Salesforce Lead. Contacts with lifecycle stage of qualified, opportunity, or customer map to Salesforce Contact attached to a parent Account. The split rule is defined during scoping based on the customer's Aritic lifecycle stage matrix. The original Aritic lifecycle stage is preserved in a custom field aritic_lifecycle_stage__c on both Lead and Contact for audit trail and reporting continuity.

Aritic Company records map to Salesforce Account. Company name becomes Account Name; domain becomes Website. Account is imported first to establish the foreign-key chain for downstream Contact imports. Multi-currency companies from Aritic carry the currency code to the Account's BillingCurrencyIsoCode field if the Salesforce org has multi-currency enabled.

Aritic Deals map to Salesforce Opportunity. The Aritic pipeline maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal stage names map to Opportunity StageName values, with the stage probability percentage transferred to StageProbability. Closed-Won and Closed-Lost reasons from Aritic custom fields become Opportunity Loss Reason and custom Win Reason fields.

Each Aritic pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process whitelisting the relevant stage values. Pipeline stage order and win-loss criteria migrate from Aritic. Any stage-level automation triggers are captured in the automation inventory for manual rebuild in Salesforce Flow; they do not migrate automatically.

Aritic pipeline stages map to Salesforce Opportunity StageName values within the configured Sales Process. Stage probability percentages migrate from Aritic with rounding to Salesforce's integer requirement. Stage names that do not match Salesforce's default vocabulary become custom stage labels stored in the Sales Process.

Aritic lead score values export as static numbers at migration time and land in Salesforce as a custom number field lead_score__c on Lead and Contact. The active scoring rules (conditions, weights, triggers) do not export from Aritic. We deliver a scoring-rule inventory sheet during discovery so the customer can reconstruct the model in Salesforce Einstein Lead Scoring (Enterprise) or a custom Flow-based scoring logic post-migration.

Aritic products used in Deals map to Salesforce Product2 records. The Aritic SKU maps to ProductCode; product name maps to Name. Standard Pricebook entries are created during import. Products are imported before Line Items to satisfy the Product2 reference.

Aritic Deal Line Items map to Salesforce OpportunityLineItem. We resolve the Pricebook2 reference, the Product2 reference, and the parent Opportunity at migration time. Quantity, UnitPrice, and TotalPrice migrate directly. If Aritic line items carry a discount percentage rather than a calculated net price, we compute the net price before insert.

Aritic call activities map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL transfer to custom Task fields. The ActivityDate timestamp is preserved to maintain activity timeline ordering. WhoId points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account.

Aritic email activities migrate to Salesforce EmailMessage records for content and a linked Task record for the activity timeline entry. The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account. Attachments on emails migrate as ContentDocument records linked via ContentDocumentLink.

Aritic meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendees link via EventRelation records pointing at the migrated Leads, Contacts, and Users. The original Aritic timestamp is preserved as ActivityDate on the parent Task record if Aritic logs meetings as both an Event and a Task.

Aritic Tasks map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignments migrate by resolving Aritic owner IDs to Salesforce OwnerId via the User mapping. Overdue and completed task states transfer as-is.

Aritic Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Note body transfers as plain text with rich-text formatting preserved where Aritic stores it. Notes without a resolvable parent record are held in a queue for manual assignment post-migration.

Aritic File Manager documents migrate as Salesforce ContentDocument records organized by Contact and Deal ID. Files are downloaded from Aritic into a migration bundle before re-upload. Some Aritic files are stored as URL references rather than binary blobs; these are flagged as broken links and re-uploaded manually if the external URL has expired.

Aritic invoice records including line items, totals, currency, and payment status map to Salesforce. If the destination Salesforce org does not have Financial Services Cloud or a billing app, invoice records map to a custom Invoice object with a PDF attachment preserved from Aritic. Multi-currency amounts transfer with the currency code; exchange rates at migration time are captured in a custom field for reconciliation.

Aritic custom fields on Contacts, Companies, and Deals are enumerated during discovery and mapped to Salesforce custom fields of equivalent type. Picklist-type custom fields in Aritic map to Salesforce picklist or multi-select picklist fields with the same value set. Formula-type custom fields do not migrate; they are flagged during scoping and documented for rebuild as Salesforce formula fields or Flow assignments.

Aritic tags stored as comma-separated values on Contacts and Deals map to Salesforce multi-select picklist fields. Tags used for segmentation purposes are flagged during scoping; segmentation rules built in Aritic do not export and must be rebuilt in Salesforce as filtered views or Campaigns.

Aritic workflow rules, sales triggers, automation sequences, and task creation rules do not export in a transferable format. We do not migrate them. We document every active Aritic workflow during the discovery phase and deliver a written automation inventory with the trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin rebuilds them in Salesforce Flow post-migration.

Aritic owner references on Contact, Company, Deal, and Activity records resolve by email match against Salesforce User records in the destination org. Owners without a matching Salesforce User go to a reconciliation queue. The customer's Salesforce admin provisions missing Users (active or inactive based on whether the original Aritic user is still employed) before the production migration phase begins. Inactive users are preserved as read-only records to maintain historical accuracy.