Migrate from Oracle CRM On Demand to Twenty CRM

Oracle Account records map directly to Twenty Company records. We normalize the Account Name, extract and structure address records (address fields from Oracle's location structure map to Twenty's address compound fields), and assign the Owner to the corresponding Twenty User resolved by email match. Oracle Account Type (Customer, Prospect, Partner, Competitor, etc.) maps to a Twenty custom field since Twenty's standard Company model uses a single Companies object without a built-in type classification.

Oracle Contact records map to Twenty Person records. We preserve name fields (first, last, title), email (used as dedupe key during import), phone, and any custom fields. Contact-to-Account linking is preserved by resolving the Oracle AccountId to the corresponding Twenty Company record on the Person's company_id field. Email deduplication runs against the Person table to prevent duplicate Person records for shared email addresses across the organization.

Oracle Leads require a split decision during migration scoping. If the source tenant is on the Enterprise Lead Referral tier, lead records are create-only via API with no edit or convert capability, meaning historical lead data may be limited. For standard tier tenants, we assess the Lead record state: Leads that are unqualified prospects map to Twenty Person records in a 'Lead' context; Leads that have been worked and contain sales activity may be converted in Oracle and migrate as Person records with opportunity associations. The Oracle Lead_Source and Lead_Status fields map to Twenty Person custom fields for attribution and status tracking.

Oracle Opportunity records map directly to Twenty Opportunity records. StageName, Amount, Probability, Close_Date, and Description transfer directly. Oracle's Opportunity-to-Account association maps to Twenty's opportunity.company_id pointing to the migrated Company. Opportunity-to-Contact associations map via Twenty's opportunity.personId pointing to the migrated Person. We flag Opportunity records with no associated Account for admin reconciliation before production import.

Oracle Task records map to Twenty Task records with Status, Priority, Subject, and due date preserved. Task assignment migrates by resolving Oracle's OwnerId to the Twenty User mapping table. Oracle's Task types (Call, Follow-up, Email, etc.) map to a Twenty custom task_type field since Twenty's standard Task model does not enforce a TaskSubtype enumeration. Activity ordering is preserved by setting Task due_date to the original Oracle timestamp.

Oracle Call records map to Twenty Task records with task_type set to Call. Oracle call disposition, duration (Call_Duration_Secs), and notes migrate to Twenty custom fields on the Task. The WhoId (Contact or Lead reference) resolves to the corresponding Twenty Person. The WhatId (Opportunity or Account reference) resolves to the corresponding Twenty Opportunity or Company. Call recording URLs stored in Oracle custom fields migrate as Task attachment references if Twenty's attachment model supports URL-based linking.

Oracle Appointment records map to Twenty Task records with task_type set to Meeting. Oracle's Start_Time and End_Time map to Twenty's due_date and due_date (or separate meeting_start and meeting_end custom fields if configured). Location migrates to a custom field. Attendee associations (Contact and Lead attendees) migrate to a meeting_attendees relationship if Twenty supports multi-person meeting records; otherwise, individual Task records are created per attendee with meeting metadata preserved.

Oracle Custom Objects vary per tenant and require schema reverse-engineering from the source API before mapping. We extract the custom object definition (field names, types, relationships) via Oracle's REST API during discovery. Custom objects that reference standard objects (Account, Contact, Opportunity) map to Twenty custom objects with corresponding relationship fields. Custom objects that represent denormalized data (address lists, product catalogs) may be consolidated into a single Twenty custom object or linked via the company_id relationship depending on the data model intent.

Oracle Named Users map to Twenty User accounts. We resolve by email match during migration. Any Oracle Owner referenced on a record but without a corresponding Twenty User is placed in a reconciliation queue for the customer's admin to provision. OwnerId references on Account, Contact, Opportunity, and Activity records are resolved at migration time against the User mapping table.

Oracle record attachments export via Oracle's bulk export or API. We map file name, content type, and blob data to Twenty's attachment model if the target instance supports blob attachments. URL-based attachments (links to Oracle document management) migrate as URL fields on the target record. Large attachment volumes (thousands of files) require separate scoping because storage provisioning on the self-hosted Twenty instance is a customer infrastructure decision.