Migrate your Ortto data

Ortto's primary contact object. We perform standard field mapping for all standard fields (name, email, phone, location, lifecycle stage). Custom fields up to 100 are fully migratable via the Person custom-field API endpoints.

Account object supports up to 3,000 people linked per account and 25 custom fields. We map account fields and relationships directly. The Accounts API endpoint is separate from the People endpoint and requires distinct API calls.

Audiences are dynamic or static segments of People. Export via CSV from the Segments UI or via API. We convert audience definitions into equivalent segment rules in the destination platform, noting any field or operator differences.

Tags are a first-class object in Ortto's API. We export tag assignments per person and recreate them at the destination, preserving the tag taxonomy.

Activities represent behavioral events (email opens, form submissions, custom events). The Activity API returns up to 100 activities per feed view. We paginate through activity history but note that legacy activities older than the retention window may not be retrievable.

Campaigns (email, SMS, push) can be exported individually or in bulk from the UI as CSV. Campaign content (templates, body copy, assets) requires separate export. We flag any campaign schedules that may conflict with destination platform send policies.

Up to 100 custom fields per Person. We export field definitions (name, type, options) and create corresponding fields in the destination before migrating values. Aggregate field types are not supported in Ortto's API and are flagged if present.

Limited to 25 custom fields per Account (Organization). We map these but note that destination platforms with different field type restrictions may require type conversion or text concatenation for multi-select options.

Ortto's dashboard configurations (widget types, chart settings, cohort report definitions) are not programmatically exportable. We document the dashboard structure and data sources so your team can rebuild them manually in the destination platform.

Forms support up to 50 fields. We export field mappings and widget configurations. Visual styling and layout must be rebuilt in the destination as these are UI-layer configurations not accessible via API.

KB articles and categories can be exported. We pull article content and category structure but note that rich media embeds and internal linking may need manual adjustment in the destination CMS.

Data source integration logs (up to 100 entries displayed) are transient operational data not meaningful for migration. We do not attempt to preserve these.

Journey/automation definitions cannot be exported via API or CSV from Ortto. We capture screenshots and document the flow structure during discovery but the automation logic must be manually rebuilt in the destination platform.

Custom role creation is plan-dependent. We export user role assignments and permission sets where available and map them to equivalent roles in the destination platform, flagging any permissions that have no direct equivalent.