Migrate your Aritic Sales CRM data

Standard contact records with name, email, phone, company association, lifecycle stage, and custom properties. We map 1:1 for most sources; we flag duplicate email addresses and empty required fields before import.

Company/Account records hold address, industry, size, and can be linked to multiple Contacts. We import Companies first to establish foreign-key relationships for downstream Contact imports.

Deals support 360-degree views, milestones, conversion probability, and stage history. We preserve deal stage names as custom mapping if the destination uses different stage terminology.

Multiple pipelines are supported on all plans. We migrate the full pipeline structure including stage names, order, and win/loss criteria. Automation triggers attached to pipeline stages require rebuilding in the destination.

Each pipeline has ordered stages with optional stage-specific automation. We map stage names and carry forward the ordering; any stage-level automation is flagged as a workflow gotcha for the customer.

Tasks are linked to Contacts or Deals with due dates, assignees, and completion status. We migrate open and closed tasks; completed task history is preserved but may not carry the full activity log.

Activity records capture calls, emails, and meetings logged against a Contact or Deal. Some sources treat Activities as separate objects; we merge them into the target CRM's activity model and preserve the activity type as a custom property.

Lead scoring rules and scores are stored per Contact. Scoring models vary by source CRM, so we export the score value and map it to the destination's lead scoring field; the scoring rules themselves require manual recreation.

Aritic's File Manager holds documents, images, and deal-related files. Files export as individual downloads; we bundle them into a ZIP organized by Contact and Deal ID for re-import. Some attachments may be stored as URLs rather than binary blobs.

Invoice records include line items, totals, currency, and payment status. We map invoice fields to the destination's invoice or estimate object; multi-currency invoices require explicit currency mapping.

E-contract signatures and quote documents are supported on Professional. These are treated as related records linked to Deals; signature status and version history are preserved as custom properties in the destination.

User records include name, email, role, and performance metrics. We map owner assignments on Deals and Tasks; inactive users are preserved as read-only records to maintain historical accuracy.

Custom fields added by the customer on Contacts, Companies, or Deals are enumerated during scoping. We map each custom field explicitly; any custom field with a picklist or formula-type behaviour is flagged for value mapping before import.

Tags applied to Contacts and Deals are exported as a comma-separated list and mapped to the destination's tagging or label system. Segmentation rules built in Aritic do not export and must be rebuilt.

Aritic workflow rules (sales triggers, automation sequences, task creation rules) do not export in a transferable format. We do not migrate them; we document the full list of active workflows so the customer can rebuild them in the destination system.