Migrate from AdOrbit to Twenty CRM

AdOrbit Contacts map directly to Twenty CRM People. The AdOrbit contact's email, phone, job title, address, and custom fields migrate to the corresponding Twenty People fields. The contact's linked Company (advertiser/vendor) reference resolves via the company mapping. We sanitize all field values before CSV staging per AdOrbit's comma-scrubbing requirement.

AdOrbit Advertiser records map to Twenty CRM Company. The Advertiser-Contact relationship is preserved through the Company-People relationship in Twenty. Classification (advertiser/vendor/partner) from AdOrbit's company type field maps to a custom picklist field that we add to the Twenty Company object during schema pre-build.

Ad Tickets are media-specific records without a native Twenty CRM equivalent. We create a custom object named Ad Ticket in Twenty's Data Model with fields for ticket type (print/digital/service), status, publication reference, placement details, CPM/fixed pricing terms, and attachment URLs. Ticket type taxonomies and custom ticket fields from AdOrbit map to corresponding custom fields on the Twenty Ad Ticket object.

AdOrbit Orders (which flow from Proposals) map to Twenty CRM Opportunity. The order's pricing terms (fixed, CPM, hybrid), billing schedule, and e-signature status migrate to Opportunity fields. Media-specific line items from the order require a custom line item approach: we map the primary line item to Opportunity fields (name, amount, close date) and document remaining line items as a structured note attachment for the customer's admin to configure in Twenty.

AdOrbit Proposals map to Twenty CRM Opportunity with a status field reflecting the proposal lifecycle (Draft, Sent, Accepted, Lost). Proposal pricing terms, validity dates, and e-signature status migrate as Opportunity custom fields. Accepted proposals that generated Orders carry the linked Order reference in a custom Opportunity field.

AdOrbit Freelancer Management records (Professional and Enterprise tiers) contain rate, assignment, and billing data. Freelancer contact details migrate as Twenty People records. Rate and assignment data migrate to custom fields on the People record (freelancer_rate__c, freelancer_assignment__c). The customer's admin decides whether to flag active freelancers via a custom status picklist or via a separate custom Freelancer object.

AdOrbit Subscription Management records (billing frequency, subscriber status, recurring amount) migrate as People records with subscription-related fields in custom properties. The subscriber's contact information is primary; billing details migrate as custom fields on the People record or to a subscription-specific custom object if the customer requests a separate table.

Publications and MagBuilder Layouts define print layout context for ad tickets. Publication metadata (name, frequency, circulation, layout specs) migrates as a custom Publication object in Twenty. Layout files export from AdOrbit via file sharing (FTP or Dropbox) and transfer as ContentDocument attachments linked to the Publication record.

Digital Media and Inventory Module tracks available ad slots and placements. These non-standard CRM objects migrate as a custom Inventory Slot object in Twenty with fields for placement name, slot type, dimensions, availability status, and associated Publication reference. Availability data is preserved as of migration date; live inventory sync requires post-migration configuration with the customer's ad ops tool.

Twenty CRM does not include a native billing or accounts receivable module. Invoice records and open AR aging data migrate as Note records with structured fields (invoice_number__c, amount__c, status__c, aging_days__c) attached to the relevant Company or People record. The customer sets up a separate accounting integration post-migration for live invoice management.

AdOrbit Vendor records (personnel/vendor/subscriber classification) map to Twenty CRM Company with a vendor classification flag. Vendor-specific fields (tax code, payment terms) migrate as custom Company fields. Vendor records are imported alongside advertiser and partner company records using the bulk CSV workflow.

AdOrbit Users with role-based permissions and sales rep assignments on orders and tickets map to Twenty CRM Users. Owner references on Contacts, Companies, and Opportunities resolve via the User mapping table by email match. Unresolved owners are held in a reconciliation queue for the customer's admin to provision before record import continues.