Migrate from Ortto to Twenty CRM

Ortto People map directly to Twenty Person. Standard fields (first_name, last_name, email, phone, city, country, lifecycle_stage) map to Twenty's equivalent Person fields. We export all custom fields (up to 100 supported) and pre-create corresponding fields in Twenty's Settings Data Model before import. Ortto's lifecycle stage values migrate as a text field on Person for audit continuity. Email addresses serve as the primary dedupe key during CSV import.

Ortto Accounts (formerly Organizations) map to Twenty Company. Each Account can link up to 3,000 People in Ortto; we resolve the Person-Company relationship during import by matching the Account ID stored on each Person record. Custom fields (up to 25) on Accounts migrate to custom fields on Twenty Company. Company domain becomes the website field and is used as a secondary dedupe key.

Ortto Activities represent behavioral events (email opens, form submissions, page views, custom events). We split by type: marketing events (opens, clicks) migrate as Note records linked to the Person; operational events (calls, meetings, custom trackable actions) migrate as Task records with the original timestamp preserved as ActivityDate. The Activity API returns up to 100 per feed view — we paginate through the full history. This mapping preserves the activity timeline against the correct Person record using WhoId resolution.

Tags are first-class objects in Ortto's API and export as a per-Person tag list. We export all tag assignments, normalize them, and create corresponding Tag records in Twenty. Tags applied to multiple objects (Person, Company, Activity) require separate Tag relation records in Twenty. The original tag taxonomy (naming conventions, tag groups) is preserved to support post-migration segmentation.

Ortto Audiences are dynamic or static segments of People defined by filter rules. Twenty does not have a native Audience or Segment object. We convert audience definitions into Twenty Tags (for static segments) or documented filter criteria (for dynamic segments) that the customer's team can recreate as saved views in Twenty. The mapping notes include the original audience rule logic so the segment can be rebuilt manually.

Ortto Campaigns (email, SMS, push) have no direct Twenty equivalent since Twenty lacks a native campaign management object. We map campaigns to Twenty Opportunity records using a naming convention that preserves the original campaign name, with campaign type stored as a custom picklist field. Campaign status (draft, active, completed) maps to Opportunity Stage. Campaign UTM parameters and source data migrate as custom fields on the Opportunity.

Up to 100 custom fields per Person are fully migratable. We export field definitions (name, type, options) and create corresponding fields in Twenty's Settings Data Model before migrating values. Aggregate field types (a known Ortto API limitation) are flagged during discovery for manual post-migration recreation. Multi-select and date field types require type mapping to their Twenty equivalents.

Up to 25 custom fields per Account migrate to Twenty Company custom fields. Field type restrictions in Twenty may require type conversion (for example, multi-value selects stored as comma-separated text). We document any required transformations during discovery and apply them during the transform step before import.

Capture widgets (forms and pop-ups) do not migrate. Ortto forms support up to 50 fields with visual styling configured in the UI layer. We export the field structure and mapping logic as a written inventory. The customer's team rebuilds forms using Twenty's built-in form fields or an external form tool (Typeform, Tally, or a custom form) and connects submissions via webhook to Twenty's API.

Journey/automation definitions cannot be exported via API or CSV from Ortto. We capture screenshots and document the flow structure during discovery (trigger conditions, branches, delays, CRM actions) as a written inventory. Twenty's workflow builder provides a starting point for reconstruction, but the customer's team or a Twenty implementation specialist rebuilds the logic manually post-migration.

Ortto dashboard configurations and cohort report definitions are not programmatically exportable. We document the dashboard structure, widget types, data sources, and filter definitions as a written inventory. Twenty's analytics views and charts are rebuilt by the customer's team in Settings.

Ortto user role assignments and permission sets (available on Business and Enterprise tiers) are exported where available. Twenty uses a workspace-based permission model with Members and a limited role structure that is still maturing. We map Ortto role names to the nearest Twenty equivalent and flag any permissions that have no direct counterpart in Twenty so the customer's admin can configure access manually.