Migrate from Ortto to Pipedrive

Ortto People map directly to Pipedrive Person records. Standard fields (name, email, phone, location, title) migrate with direct field mapping. Custom fields up to the plan limit (100 on Professional, 150 on Business, 200 on Enterprise) create equivalent Pipedrive custom fields on Person before migration. Note that Pipedrive caps custom fields at approximately 82 total across all objects on non-Enterprise tiers; we flag any field count that exceeds the destination tier limit during discovery and discuss field consolidation or tier upgrade before migration begins.

Ortto Account records (formerly Organizations) map to Pipedrive Organization. The Account API endpoint is separate from the People endpoint in Ortto, and we handle them independently before resolving the Person-to-Organization link via the Organization ID on the Person record. Ortto's 3,000-person-per-account limit and 25 custom field limit on Accounts (50 on Enterprise) map to Pipedrive's Organization custom field budget. Pipedrive Organizations do not have a hard per-record contact cap, but we flag accounts with unusually large Person counts so the customer can decide on organization structure post-migration.

Ortto links People to Accounts natively in its data model. We preserve the relationship during migration by resolving the Ortto Account ID to the Pipedrive Organization ID and setting the Organization ID on each Person record at import time. If a Person in Ortto is linked to multiple Accounts, we flag this as a multi-org scenario and discuss whether to create multiple Person records or use Pipedrive's relationship fields during scoping.

Ortto Audiences (dynamic segments based on field conditions or static lists) have no direct Pipedrive equivalent. We translate dynamic audience rules into Pipedrive Filters that the customer can save and reuse within Pipedrive's filter builder. Static audience memberships migrate as Pipedrive Lists with Person membership records. Note that Pipedrive Lists do not support dynamic rule-based membership update post-migration; we document the original audience rules so the customer can recreate dynamic segments using Pipedrive's filter API if needed.

Tags are a first-class object in Ortto's API and are exported per Person with their full taxonomy. We migrate tag assignments as Pipedrive Labels attached to Person and Organization records. Pipedrive Labels are a multi-select label system available on all paid tiers. The original Ortto tag names and taxonomy structure are preserved; Pipedrive does not support hierarchical tags, so any nested tag taxonomy in Ortto flattens into a flat label namespace with naming convention preserved.

Ortto Activities (email opens, form submissions, custom events, web visits) map to Pipedrive Activity records. The Activity API in Ortto returns up to 100 activities per feed view; we paginate through the full activity history. Pipedrive Activities are linked to Person or Organization records via the id value. Note that Pipedrive has a different activity type model than Ortto; we map Ortto activity types to the closest Pipedrive Activity type (call, email, meeting, task) and preserve the original activity metadata in custom fields on the Activity record. Very large activity histories may require token budget management on the Pipedrive API side.

Ortto Campaigns (email, SMS, push, transactional) do not have a direct Pipedrive equivalent. Pipedrive does not store campaign content as a CRM object. We do not migrate campaign records, templates, or scheduling data. We export a CSV inventory of all Ortto campaigns with their audience rules, content summary, and scheduling metadata so the customer's marketing team can rebuild campaigns in their chosen email marketing platform (Brevo, ActiveCampaign, Klaviyo) or in Pipedrive Campaigns if that product is licensed.

Up to 100 custom fields per Person on Ortto Professional map to Pipedrive Person custom fields. Field type conversion is required: Ortto aggregate fields cannot be created via API and are flagged for manual recreation in Pipedrive. Multi-select picklist fields in Ortto map to Pipedrive multi-select options fields. Date, numeric, text, and boolean types map directly. Long text fields in Ortto map to Pipedrive text fields; Pipedrive does not have a separate long-text field type. We pre-create all custom field definitions in Pipedrive before migrating any Person records.

Ortto Account custom fields (up to 25 on Professional, 50 on Enterprise) map to Pipedrive Organization custom fields. The same type-conversion rules apply as for Person custom fields. Aggregate field types on Accounts are flagged during discovery for manual handling. Pipedrive's per-field custom field limit per object is approximately 82 on non-Enterprise tiers; we check the combined custom field count across Person and Organization during scoping to avoid hitting this limit mid-migration.

Ortto journey and automation definitions are not programmatically exportable. We do not migrate them. We perform a manual discovery session to document every active journey: entry trigger, condition shapes, action shapes, delay configurations, and exit criteria. This documentation is delivered as a written reconstruction guide. The customer's team rebuilds journeys in Pipedrive Workflows (if licensed) or a third-party automation tool. The automation rebuild is outside standard migration scope.