Migrate your AdOrbit data

Standard CRM contact records with customizable fields, email uniqueness controls, and bulk CSV import via the Historical Data Tool. We import contacts directly using the platform's Sheets upload workflow and validate against the Require Unique Email Address configuration.

Company records in AdOrbit are tightly linked to Contacts and support vendor/client/partner classification. We preserve the company-contact relationship during migration by sequencing company imports before contact imports and maintaining cross-reference IDs.

Ad Tickets are the core campaign execution record, spanning print, digital, and service ticket types with status tracking and asset attachments. Field names and ticket type taxonomies vary between AdOrbit instances; we map these to destination campaign or job objects and flag any custom ticket fields for manual review.

Orders flow from proposals and can carry pricing terms (fixed, CPM, hybrid), billing schedules, and e-signature status. The order schema includes media-specific line items that require value-level mapping when migrating to generic CRM deal objects.

AdOrbit's finance module generates invoices tied to executed orders. Open invoice status, aging, and payment method fields do not map 1:1 to standard CRM invoice objects; we map invoice records to destination invoice or billing objects and flag outstanding balances for reconciliation.

Digital Media and Inventory Module tracks available ad slots, placements, and availability. These are non-standard CRM objects; we export them as custom records or map them to destination inventory/placement objects depending on the target system.

Publications and MagBuilder Layouts define the print layout context for ad tickets. Layout files and publication metadata are exported via the file sharing export; we transfer these as attachments or link references rather than importing the binary layout files themselves.

Subscription Management module handles recurring billing for subscribers. Subscription records including billing frequency and subscriber status are fully migratable as contacts with subscription properties.

Vendor records are part of the Contacts and Companies module and support personnel/vendor/subscriber classification. We import vendors alongside other company records using the bulk CSV import.

Freelancer Management is available on Professional and Enterprise tiers. Freelancer records include rate and assignment data; we import them as contacts or custom objects depending on the destination system's schema.

Project Management and task tracking are available on higher tiers. Task dependencies and assignees map to destination task or work-order objects; automation workflows attached to projects are flags rather than migratable logic.

AdOrbit supports custom fields on tickets and contacts. We extract the full custom field schema during discovery, then map each to destination custom fields, preserving option lists and conditional logic where the target system supports it.

Ticket assets and uploaded files can be exported to FTP or file sharing based on ticket status (Non-Final, Final, All). We transfer these via the configured export destination or direct download during migration, preserving the status-based folder structure.

User records include role-based permissions and sales rep assignments on orders and tickets. We import users as destination users and map order/ticket owner references to maintain historical accountability.