Migrate from AdOrbit to Zoho CRM

AdOrbit Contacts migrate directly to Zoho Contacts. The contact's advertiser or vendor classification from the AdOrbit role field maps to a Zoho custom picklist field contact_role__c. Email uniqueness controls in AdOrbit carry over as dedupe validation in Zoho. We stage CSV via Zoho's Data Migration wizard after comma-scrubbing all field values.

AdOrbit Company records (advertiser classification) map to Zoho Accounts. The HubSpot-style domain field in AdOrbit becomes the Account Website. We import Accounts before Contacts so that the Account-Contact linkage is satisfied at insert time. Vendor and partner classifications become Account custom fields rather than separate objects.

AdOrbit Orders (originating from Proposals with pricing terms including fixed, CPM, and hybrid) map to Zoho Deals. The order status maps to a Zoho custom picklist ad_order_status__c because Zoho Deal stages are pipeline-scoped. Pricing terms and billing schedules migrate as custom fields on the Deal record.

AdOrbit Proposals split into Zoho Deals (for the sales pipeline record) and Zoho Creator or custom Quote records (for the pricing document). E-signature status from AdOrbit migrates as a custom field attached to the Quote. Proposals without a linked Order become Deals at zero amount pending proposal-to-order conversion in Zoho.

Ad Tickets (the core campaign execution record covering print, digital, and service ticket types) have no Zoho standard equivalent. We create a Zoho custom module Ad_Ticket__c with custom fields matching the ticket type taxonomy, status tracking, and asset attachment fields from AdOrbit. Ticket type (print, digital, service) becomes a custom picklist field.

AdOrbit Digital Media and Inventory Module (availableity slots, placements) exports as a custom Zoho module with fields for slot_name, placement_type, publication_reference, availability_status, and rate_card. We create the custom module schema during scoping and import inventory records as custom object rows with lookups to the relevant Account and Ad_Ticket__c.

AdOrbit Publications and MagBuilder Layouts define print layout context for ad tickets. Publication metadata (name, frequency, circulation) migrates to a custom Publications__c module. MagBuilder layout files export as attachments transferred via file sharing (FTP or Dropbox export per the configured status rule) and reattached to the Zoho Publication record.

AdOrbit Subscription Management records (recurring billing, subscriber status, billing frequency) migrate as Zoho Contacts with subscription custom fields: subscription_status__c, billing_frequency__c, and renewal_date__c. Subscriber revenue history migrates to a related custom object Subscription_Revenue__c if the customer requires it.

AdOrbit Vendor records use the same Companies module with a vendor classification tag. We import vendors as Zoho Accounts with a vendor_type__c custom field set to Vendor. Personnel vendors (individual freelancers) import as Contacts with the vendor_type__c field set to Personnel.

AdOrbit Freelancer Management records (available on Professional and Enterprise) include rate and assignment data. We import freelancers as Zoho Contacts with freelancer_rate__c, assignment_status__c, and skills__c custom fields. Freelancer assignments migrate as Tasks linked to the Contact.

AdOrbit Users with role-based permissions on Orders and Tickets map to Zoho Users. We match by email address and flag any AdOrbit Owner reference without a matching Zoho User for admin provisioning before production migration begins.

AdOrbit ticket assets export based on the configured status rule (Non-Final exports all uploads until marked final, Final exports only after status set, All exports on every upload). We check the status rule during scoping, then transfer attachments to Zoho via the Attachments module linked to the corresponding Ad_Ticket__c record.