Migrate from Aritic Sales CRM to Pipedrive

Aritic Company records map to Pipedrive Organization in a 1:1 relationship. We import Organizations first in the migration sequence to establish foreign-key references that Contacts depend on during insert. The Aritic company domain maps to the Organization's Website field. Any Aritic custom fields on Company records are enumerated during scoping and mapped to Pipedrive custom fields on the Organization object before migration.

Aritic Contact maps to Pipedrive Person. Email deduplication runs against the Person email field before insert to prevent duplicate records. Aritic's lifecycle stage maps to a custom text field for audit. All Aritic custom contact properties are enumerated during scoping and mapped to equivalent Pipedrive Person custom fields. Required field validation (name, email format) is applied before each batch insert.

Aritic's non-hierarchical relationship model lets a Contact link to multiple unrelated Companies, used for tracking deal influencers outside the primary account hierarchy. Pipedrive Person supports a single primary Organization lookup. We map the primary Company association directly and store additional linked Company names as a comma-separated custom field (secondary_organizations__c) on the Person record. Any Contact with more than one associated Company is flagged in a post-import reconciliation report for the customer to verify.

Aritic Deals map to Pipedrive Deals with a 1:1 mapping on the core deal fields: title, value, stage, expected close date, owner, and currency. Aritic milestone and conversion probability data map to custom number fields on the Deal. Deal stage names from Aritic are preserved as custom fields or mapped to Pipedrive stage labels depending on the target pipeline structure. Closed-won and closed-lost reasons from Aritic custom properties map to Pipedrive custom text fields.

Aritic Pipelines are migrated as Pipedrive Pipeline configuration. We create Pipedrive Pipelines using Pipedrive's Pipeline API or settings, preserving stage names, order, and win/loss criteria. Aritic's stage-specific automation triggers do not migrate and are flagged in the workflow inventory. Stage probability percentages map to Pipedrive stage probability fields where available.

Aritic call Activity records map to Pipedrive Activity records with type = call. Call duration, disposition, and recording URL from Aritic map to Pipedrive Activity custom fields. Activity timestamps are preserved by setting the Pipedrive Activity start time to the original Aritic timestamp. Owner assignment is resolved by matching the Aritic owner email to the Pipedrive User.

Aritic email Activity records map to Pipedrive Activity records with type = note, with the email body stored in the activity content field. Email subject, sender, recipient, and timestamp are stored in custom fields or in the note body depending on the target configuration. If Aritic tracked email status (sent, delivered, bounced), that data is preserved as a custom field on the Activity.

Aritic meeting Activity records map to Pipedrive Activity with type = meeting. Start time, end time, location, and attendee list are preserved in the Activity record. The activity is linked to the related Person or Deal using the Aritic relationship data carried forward during the export phase. Meeting notes from Aritic are stored in the Pipedrive Activity content field.

Aritic task Activity records map to Pipedrive Activity with type = task. Task status, priority, due date, and description migrate directly. Completion status is set using the Aritic task completion flag. Assignee is resolved via owner email matching against the Pipedrive User table. Open tasks are imported first, followed by completed task history.

Aritic lead score values are exported at migration time and mapped to a custom number field (person_score__c) on the Pipedrive Person object. The active scoring model (rules, conditions, weights, and triggers) is stored separately in Aritic and is not portable. We deliver a scoring-rule inventory sheet listing each active rule with its logic so the customer's Pipedrive admin can reconstruct the model manually. This inventory is a separate deliverable from the data migration.

Aritic File Manager documents and deal-related attachments are downloaded and bundled into a ZIP organized by Contact ID and Deal ID. We handle both binary file attachments and URL-based attachments by downloading referenced files before bundling. If an external URL has expired or the file is no longer accessible, that attachment is flagged as a broken link in the migration report for the customer to resolve. The ZIP is re-imported to Pipedrive using the Files API.

Aritic Invoice and Estimate records are mapped to custom fields on the related Pipedrive Deal: invoice_number, invoice_total, currency, and payment_status. Line item details are stored as a custom text or JSON field on the Deal. Signed e-contract documents and quote PDFs migrate as Files attached to the Deal. Multi-currency invoices require explicit currency mapping confirmed during scoping.

Aritic Tags applied to Contacts and Deals are exported as a comma-separated list per record. Tags are mapped to Pipedrive Label records and linked to the Person or Deal using Pipedrive's label API. Segmentation rules built in Aritic are not transferable and are documented in the segmentation inventory for the customer to rebuild as Pipedrive Label groups or as static Lists.