Migrate from AdOrbit to Freshsales

AdOrbit Contact records map directly to Freshsales Contact. We preserve the firstname, lastname, email, phone, mobile, jobtitle, and custom property fields. Email serves as the dedupe key during import. The contact-to-company linkage is preserved by importing Accounts before Contacts and resolving the AccountId on each Contact import.

AdOrbit Company records (including advertiser, client, vendor, and partner classifications) map to Freshsales Account. The company name becomes Account Name, domain becomes Website, and address fields map to Billing Address. Classification type from AdOrbit's company type property maps to a custom picklist field adorbit_company_type__c.

AdOrbit Orders map to Freshsales Deals. The order name becomes Deal name, total amount becomes Amount, expected close date maps to Close Date, and order status maps to Deal stage. AdOrbit pricing terms (fixed, CPM, hybrid) preserve in a custom field adorbit_pricing_term__c. Owner resolution happens by email match to Freshsales User.

AdOrbit Ad Tickets (print, digital, service ticket types) map to Freshsales Deals with custom fields added to capture ticket type, ticket status, publication reference, insertion dates, and asset attachment URLs. The ticket type taxonomy varies between AdOrbit configurations; we extract the full custom field schema during discovery and create matching Freshsales custom fields before migration.

AdOrbit Proposals (which flow into Orders) map to the same Freshsales Deal with proposal-specific custom fields: proposal_status, proposal_version, and e_signature_status. E-signature status does not migrate as a live integration; we flag the last-known status value for the customer's admin to reconcile with DocuSign or HelloSign post-migration.

AdOrbit invoice records (with open status, aging, and payment method) map to Freshsales custom invoice fields on the Deal object: adorbit_invoice_number__c, adorbit_invoice_status__c, adorbit_balance_due__c, adorbit_payment_method__c. AdOrbit's AR module connects to QuickBooks Online at additional cost; Freshsales has no native two-way accounting sync, so invoice records migrate as data without live ERP linkage.

AdOrbit Subscription Management records (billing frequency, subscriber status, subscriber type) migrate as custom fields on Freshsales Contact: adorbit_subscription_status__c, adorbit_billing_frequency__c, adorbit_subscription_type__c. Recurring revenue tracking through Freshsales requires manual rebuild in Freshsales Reports or a revenue recognition integration post-migration.

AdOrbit user records with role-based permissions map to Freshsales User by email match. Sales rep assignments on AdOrbit Orders and Tickets resolve to Freshsales OwnerId via the User mapping table. Any AdOrbit user without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import.

AdOrbit vendor and freelancer records (with rate and assignment data on Professional and Enterprise tiers) migrate as Contacts or as Accounts depending on the customer's preference. Rate information preserves in a custom field adorbit_rate__c. Assignment history migrates as task or note records linked to the Contact or Account.

AdOrbit Digital Media and Inventory Module (available on Professional and Enterprise) tracks ad slots, placements, and availability. These non-standard CRM objects migrate to a Freshsales custom object named Ad_Slot__c with fields for slot_name, placement_type, publication_reference, availability_status, and rate_card. The customer configures the custom object during schema design.