Migrate from Aritic Sales CRM to Freshsales

Aritic Contacts map directly to Freshsales Contacts with the primary Company link assigned as the primary Account lookup. For contacts linked to multiple Companies in Aritic (reflecting deal influencers or stakeholder roles), we set the primary Company as the Account lookup and store the secondary Company names in a custom multi-text field secondary_accounts__c for manual verification post-import. Lifecycle stage from Aritic migrates to Freshsales Contact's lifecycle_stage property if present, otherwise to a custom picklist field.

Aritic Company records map directly to Freshsales Account. Company domain from Aritic becomes the Account website field and is used as the dedupe key during import. Industry, size, address, and phone fields map 1:1. Account records are imported first to satisfy foreign-key requirements for the Contact import phase.

Aritic Deals map to Freshsales Deals with the AccountId resolved to the migrated Account record, the primary ContactId resolved to the migrated Contact, and the OwnerId resolved via User email matching. Deal stage names migrate as Freshsales deal stage values within the target Sales Process. Closed-Lost and Closed-Won reasons from Aritic custom properties become Freshsales loss_reason and win_reason fields.

Aritic pipelines (multiple pipelines supported on all plans) map to Freshsales Sales Processes. Each Aritic pipeline becomes a named Sales Process in Freshsales with its stage sequence preserved. Stage-specific automation triggers in Aritic do not migrate; they are documented in the workflow inventory for the customer to rebuild in Freshsales Workflows.

Aritic pipeline stages map to Freshsales deal stage values within the corresponding Sales Process. Stage ordering, probability percentages, and win/loss criteria migrate from Aritic to Freshsales stage configuration. Stage-level automation triggers are flagged in the workflow inventory document and are not migrated.

Aritic Tasks linked to Contacts or Deals migrate to Freshsales Tasks with Subject, Due Date, Assignee (resolved via User email match), Priority, Status, and Description preserved. Completed task history migrates with the original completion timestamp. Task assignment to Aritic Users without matching Freshsales Users goes to the reconciliation queue.

Aritic Activity records (calls, emails, meetings) logged against Contacts or Deals migrate to Freshsales Activity records linked to the resolved Contact and Deal. Activity timestamp preserves the original Aritic timestamp for timeline ordering. Call disposition and duration data from Aritic migrate to Freshsales custom Activity fields.

Aritic's numeric lead score value migrates as a custom number field on the Freshsales Contact record. The active scoring rule logic (rule conditions, weights, triggers) is not portable. We deliver a scoring-rule inventory sheet during migration scoping so the customer's Freshsales admin can rebuild the model using Freshsales Freddy AI or custom workflow conditions, typically 1-2 hours per complex scoring rule.

Aritic File Manager documents, images, and deal-related files export as individual downloads and are bundled into the migration payload organized by Contact and Deal ID. We download URL-based attachments before migration to avoid broken links on cutover. Files re-attach to Freshsales Contact, Account, or Deal records via the Freshsales Attachments API.

Aritic User records map to Freshsales User records by email match. User name, email, and role migrate. Inactive Aritic Users are preserved as read-only User records in Freshsales to maintain historical assignment accuracy on Deals and Tasks. Users without an email match go to the reconciliation queue for manual provisioning.

Custom fields added on Aritic Contacts, Companies, or Deals are enumerated during scoping. We create matching custom fields in Freshsales before migration, using equivalent field types (text, number, date, picklist, multi-select). Picklist-type custom fields in Aritic require Freshsales picklist value creation before data import. Formula-type behaviors in Aritic custom fields are flagged for manual Freshsales formula configuration post-migration.

Tags applied to Aritic Contacts and Deals export as a comma-separated list and map to Freshsales Tags on the Contact or Deal record. Segmentation rules built in Aritic do not export; the tag inventory is provided separately for the customer to rebuild Freshsales dynamic lists if needed.