Migrate from AdOrbit to Pipedrive

Discovery and media object inventory

We audit the AdOrbit account across tier (Starter, Professional, Enterprise), object inventory (Contacts, Companies, Ad Tickets, Orders, Proposals, Media Inventory, Publications, Subscriptions, Freelancers), ticket type taxonomy, order status values, custom fields, active workflows, and file attachment volume. We pair this with a Pipedrive plan assessment: Lite ($14/user) covers People, Organizations, Deals, and Activities; Growth ($39/user) adds custom fields, multiple pipelines, and automation; Premium ($49/user) adds workflow automation and required fields; Ultimate ($79/user) adds sandbox testing and advanced security. The discovery output is a written migration scope including which AdOrbit objects migrate, which become Pipedrive custom objects, and which (invoicing, AR) require external tooling post-migration.

Schema design and custom object configuration

We design the Pipedrive destination schema. For each AdOrbit object, we specify the target Pipedrive object and any custom fields required. Ad Tickets and Orders become Deals with custom fields for ticket_type, ticket_id, pricing_type, billing_schedule, and e_signature_status. Media Inventory and Publications become custom objects (inventory_slot, publication) on Growth+ plans. We configure Pipedrive pipeline stages to match the AdOrbit order status taxonomy (Estimate, Quote, Accepted, Rejected, Invoiced, Paid) so that the stage translation matrix is defined before any data loads. Schema is validated in a Pipedrive trial or sandbox environment before production configuration begins.

CSV preparation and comma scrubbing

We extract data from AdOrbit via the Historical Data Tool CSV export and REST API. All CSV files undergo comma scrubbing as a mandatory preprocessing step: commas within field values are replaced with semicolons per AdOrbit's staging sheet requirements. Files extracted via API bypass this constraint. We generate Pipedrive-compatible CSV files for the People, Organization, and Deal imports, with custom field columns appended. Sample imports of 50-100 records per object validate field mapping before full-scale migration begins.

Test migration and reconciliation

We run a full test migration into a staging Pipedrive account using production-like data volume. The customer's admin reviews 25-50 randomly sampled records per object against the AdOrbit source, checks that custom field values populated correctly, and confirms that the pipeline stage assignments match the AdOrbit order status taxonomy. We resolve any mapping corrections (field names, picklist values, status translations) before production migration begins. This step also surfaces any duplicate records, orphaned Contacts, or missing Organization linkages that require pre-migration deduplication.

Owner reconciliation and User provisioning

We extract every distinct AdOrbit owner referenced on Contact, Company, Ad Ticket, Order, and Engagement records and match by email against the Pipedrive destination account's User list. Any AdOrbit owner without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to provision before Deal imports begin. OwnerId references on Deals and People are required at insert time, so this step gates the Deal import phase.

Production migration in dependency order

We execute the production migration in record-dependency order: Organizations (first, no dependencies), People (with OrganizationId resolved from the Company mapping), Deals from Ad Tickets (with OwnerId and OrganizationId resolved, custom fields populated), Deals from Orders and Proposals (with the same resolution), Custom objects for Media Inventory and Publications (Growth+ only, no parent dependencies), Activity history (calls, emails, meetings, tasks) linked to migrated People and Organizations via Pipedrive Activity API, and file attachments (ticket assets, order PDFs, publication layouts) linked to the parent record. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation handoff

We freeze AdOrbit writes during cutover and run a final delta migration of any records modified during the migration window. Pipedrive becomes the system of record. We deliver the full object and field mapping workbook to the customer's admin team. We provide a written inventory of every AdOrbit Automation Workflow with its trigger, conditions, and actions, with a recommended Pipedrive Workflow Automation equivalent for the customer's admin to rebuild. We do not rebuild AdOrbit workflows as Pipedrive automations inside the migration scope; that is a separate engagement or internal admin task. We support a one-week hypercare window for reconciliation issues raised during the first week of live use.