Migrate from AdOrbit to Salesforce Sales Cloud

AdOrbit Contact records migrate to Salesforce Contact directly. The contact's primary company link (advertiser, vendor, or partner classification) maps to an AccountId resolved after the Account import phase. We preserve any custom field schema extracted during discovery as Salesforce custom Contact fields.

AdOrbit Company records map to Salesforce Account. The Account is imported before any Contact phase so the AccountId lookup is satisfied at Contact insert time. Vendor, client, and partner classification from AdOrbit's company type field becomes a custom Account type picklist.

AdOrbit Advertisers are company records with an advertiser flag. We import them as Salesforce Accounts with a custom field advertiser_type__c set to true. The Advertiser-Contact linkage preserves the original relationship by resolving AccountId on each linked Contact record.

Ad Tickets are the core campaign execution record spanning print, digital, and service types. Each ticket type (print, digital, service) maps to a Salesforce Opportunity Record Type with a dedicated Sales Process. Ticket status values become Opportunity StageName values. Custom ticket fields (rate, CPM, insertion order number, publication reference) migrate as custom Opportunity fields pre-created in the destination schema.

AdOrbit Orders flow from Proposals and carry pricing terms (fixed, CPM, hybrid), billing schedules, and e-signature status. The order schema maps to Opportunity with pricing terms stored in a custom field, e-signature status in a custom field, and the total order amount in Opportunity.Amount. Order status becomes StageName.

AdOrbit Proposals map to Salesforce Quote, which is a standard object available from Professional tier. Proposal name becomes Quote.Name, status maps to Quote.Status, expiration date becomes Quote.ExpirationDate, and the related Order-Account link becomes Quote.AccountId and Quote.OpportunityId. Signed Proposal PDFs migrate as ContentDocument attached to the Quote.

Digital Media and Inventory Module slots (ad placements, available inventory, dimensions, rate cards) have no Salesforce standard equivalent. We create a custom Ad_Slot__c object with fields for slot_name, publication_reference__c, placement_type__c, dimensions__c, availability_status__c, and rate_card__c. These custom objects deploy to Sandbox for validation before production migration.

Publications and MagBuilder Layouts define the print layout context for ad tickets. We create a custom Publication__c object with fields for publication_name__c, layout_type__c, frequency__c, and publish_date__c. Publication files and MagBuilder layouts migrate as ContentDocument attached to the Publication record.

AdOrbit Subscription Management records handle recurring billing for subscribers. We create a Subscription__c custom object with billing_frequency__c, subscriber_status__c, and start_date__c linked to the Contact via a lookup. Alternatively, for simple subscriptions, properties migrate as custom Contact fields if the customer prefers a lighter schema.

Vendor records in AdOrbit are company records with a vendor classification. We import them as Salesforce Accounts with a custom field vendor_type__c set to true and a vendor_contact__c linking to the primary vendor contact record.

Freelancer Management records (Professional and Enterprise tier) include rate and assignment data. We import Freelancers as Contacts with a custom record type Freelancer and custom fields for freelancer_rate__c, assignment_status__c, and primary_publication__c lookup.

AdOrbit engagement records for calls, emails, meetings, and tasks map to Salesforce Task (for calls, emails, and tasks) and Event (for meetings). We use the Bulk API 2.0 with parent-record resolution (WhoId and WhatId) to link each activity to the migrated Contact and Opportunity. Timestamps preserve the original engagement date.

AdOrbit Project Management tasks (available on higher tiers) map to Salesforce Task with a custom Project__c lookup. Task dependencies and assignee references migrate by resolving the owner and contact relationships at migration time. Automation workflows attached to projects are flagged in the automation inventory for admin rebuild.

AdOrbit User records with role-based permissions and sales rep assignments on orders and tickets import as Salesforce Users by email match. Owner references on AdOrbit records (Contacts, Accounts, Ad Tickets, Orders) resolve to Salesforce User IDs via this lookup table. Any AdOrbit user without a matching Salesforce User goes to a reconciliation queue.

AdOrbit supports custom fields on tickets, contacts, and companies. We extract the full custom field schema during discovery, pre-create each field in Salesforce with the matching type (text, picklist, number, date, checkbox), and map values during migration. Conditional logic and visibility rules on AdOrbit fields are noted for Salesforce field-level security configuration.