Migrate from Ortto to Salesforce Sales Cloud

Ortto Person records map to Salesforce Contact if the person has an associated Account in Ortto's Organizations; they map to Salesforce Lead if no Account association exists. Ortto's lifecycle_stage property maps to a custom field ortto_lifecycle_stage__c on both Lead and Contact for audit continuity. Email addresses serve as the primary dedupe key. Any Person with an email already in Salesforce is matched and updated rather than created as a duplicate.

Ortto Organizations map directly to Salesforce Account. The Organization's domain field becomes the Account Website. The Accounts API endpoint (/v2/organizations) is queried separately from Persons, and we create all Accounts before Contact import to satisfy the AccountId Lookup requirement on Contact. Ortto supports up to 3,000 linked people per Organization; Salesforce has no practical limit on Contacts per Account.

Tags in Ortto are first-class objects referenced per Person via the People API. We export the full tag taxonomy and per-person tag assignments. Tags that represent behavioral labels (engagement level, account tier) migrate to a custom multi-select picklist field on Contact. Tags that represent topic categorization migrate to Salesforce Topics with TopicAssignment records linked to Contact or Account.

Ortto Audiences are dynamic or static segments of People defined by filter conditions. Dynamic audiences cannot be fully replicated in Salesforce because there is no equivalent dynamic query-based segment. We document each audience's filter logic and translate static audience membership into Salesforce Campaign membership (Contacts added as CampaignMembers with appropriate Status values). Dynamic audience equivalents require Salesforce Reports or a segmentation tool post-migration.

Ortto email activity events (opens, clicks, bounces) map to Salesforce Task records with a custom activity_type__c field set to email_open, email_click, or email_bounce. Email content and metadata migrate to Salesforce EmailMessage linked to the Contact or Lead. Activity timestamps are preserved on Task ActivityDate for timeline fidelity.

Ortto form submission activities map to Salesforce Task with TaskSubtype=Log and a custom ortto_form_id__c field carrying the original Ortto form identifier. Form field values that were captured and stored in Ortto custom fields migrate to corresponding Salesforce custom fields on Contact or Lead.

Ortto custom activities and events (up to 20 configurable activities synced to Salesforce per Ortto's integration documentation) map to Salesforce custom objects created with API names matching the Ortto activity name. The activity attributes migrate as custom fields on the custom object, and the activity timestamp migrates as an Event_Date__c field. Note that Ortto's native 20-activity sync limit applies to live integration, not migration; we can create more custom objects if the customer documents the schema.

Ortto Campaigns (email, SMS, push) migrate to Salesforce Campaign. Campaign Name, Status, Type, and Start/End Dates map directly. Campaign member status values (sent, opened, clicked, bounced) map to Salesforce Campaign Member Status. Campaign content (templates, body copy, assets) does not migrate via API; we export the HTML body as a Salesforce EmailTemplate ContentAsset reference and document the campaign structure for the admin to reassemble.

Ortto Person custom fields (up to 100) migrate to Salesforce custom fields on Contact and Lead. We pre-create the Salesforce custom field schema using the target field type mapping: Ortto text becomes Salesforce Text(255) or LongTextArea; Ortto number becomes Number; Ortto date becomes Date; Ortto boolean becomes Checkbox. Aggregate field types (not supported by Ortto API) are flagged during discovery and manually created in Salesforce before migration.

Ortto Account (Organization) custom fields (up to 25) map to Salesforce Account custom fields. Field type mapping follows the same rules as Person custom fields. Note that Ortto's 25-field limit is more restrictive than Salesforce Professional's 100-field limit, so there is typically room to add fields in Salesforce without hitting the ceiling.

Ortto Users mapped as CRM owners map to Salesforce Users by email match. We extract the owner assignment per Person and Organization and resolve against the destination Salesforce org's User table. Any Ortto owner without a matching Salesforce User goes to a reconciliation queue for the admin to provision before record import resumes.

Ortto Journey definitions cannot be exported via API or CSV. We capture screenshots of every active Journey during discovery and document the trigger conditions, shape sequence, delay durations, action types, and split branches in a written handoff document. The customer's Salesforce admin or a certified partner rebuilds these as Salesforce Flow record-triggered automations. This is manual work outside migration scope.

Ortto capture widget configurations (field names, labels, conditional logic) migrate as documentation. Visual styling, layout, and popup behavior do not transfer because they are UI-layer configurations not accessible via API. We export the field mapping schema so the admin can recreate the form logic in Salesforce Web-to-Lead, Experience Cloud, or a third-party form tool like FormAssembly or JotForm.

Ortto dashboard configurations (widget types, chart settings, cohort report definitions) are not programmatically exportable. We document the dashboard structure, data sources, filter logic, and widget placement during discovery so the admin can rebuild them in Salesforce Reports and Dashboards or Analytics Cloud. This is manual work outside migration scope.