Migrate from OneAdvanced Legal to Pipedrive

OneAdvanced Legal stores client name, firm/organization, contact details, and billing address in a single record. We split this into Pipedrive Person (individual name, email, phone) and Organization (firm name, website, industry). The split uses firm/organization name field from OneAdvanced Legal to create the Organization record first, then links the Person to it.

OneAdvanced Legal matters include matter type, phase, risk rating, responsible fee-earner, and client link. We map each matter to a Pipedrive Deal, setting Deal title from matter reference + client name. Matter type becomes a custom field on the Deal. Pipedrive's pipeline stages substitute for OneAdvanced Legal's phase statuses, with a value-mapping table applied per matter type.

OneAdvanced Legal time entries (Carpe Diem) capture date, duration, fee-earner, matter link, billing status, and narrative. We create Pipedrive Activities — a Task with type 'Time Entry' for billable hours, or a Note for narrative entries — attached to the corresponding Deal. Original timestamp and fee-earner attribution preserved in activity fields.

OneAdvanced Legal document metadata (file name, document type, created date, author) migrates as Pipedrive file attachments or notes on the relevant Person or Deal. The actual file content re-uploads to Pipedrive Files if the source file is accessible via API export. File size limits and unsupported formats are flagged before migration.

OneAdvanced Legal generates and stores invoices with line items, tax, and payment status. Pipedrive has no native invoicing. We preserve invoice totals, outstanding amounts, and last-payment date as custom numeric fields on the related Deal. Firms must handle invoice recreation in a dedicated accounting tool post-migration.

OneAdvanced Legal supports hierarchical client relationships (parent firm with subsidiary offices). We map these to Pipedrive Organization hierarchy using the parent_org_id field. Circular references or orphan relationships are flagged for manual resolution before the migration run. The hierarchy mapping preserves the corporate structure while ensuring no circular loops exist in the migrated data.

Nested sub-matters in OneAdvanced Legal require either a linked-Deal relationship in Pipedrive or a Parent_Matter_ID__c custom field on each Deal to preserve the hierarchy. We surface the choice before migration — linked Deals offer better UI visibility; custom fields preserve the full tree structure.

OneAdvanced Legal custom properties on clients (SRA number, referral source, client risk classification) become Pipedrive custom fields on the Person or Organization object. Field types are mapped: pick-lists to drop-downs, dates to date fields, text to text fields. Pipedrive's 40-character hash keys are generated per custom field.

Matter-level custom properties (case type, conflict-check status, indemnity-limit, statutory-body) migrate as Pipedrive Deal custom fields. Each field is created in Pipedrive's DealFields API before the migration run. Value-mapping applies for pick-list fields where OneAdvanced Legal options differ from Pipedrive's target values.

OneAdvanced Legal fee-earners and users map to Pipedrive users by email match. Unmatched users are flagged before migration — the firm either creates a Pipedrive user account first or assigns their records to a fallback owner. Active/inactive status in OneAdvanced Legal maps to Pipedrive's user active flag.

OneAdvanced Legal workflows for document production, compliance checks, and matter-quality file reviews (AI agents) have no Pipedrive equivalent. We export workflow definitions as a JSON reference document for the firm's Pipedrive admin to use when rebuilding automations in Pipedrive's automation engine.

OneAdvanced Legal integrations (The National Will Register, Cloud Forms API, legal-forms templates) are destination-specific connections that break at migration. We document each active integration as a rebuild checklist item. The firm rebuilds these connections in Pipedrive's marketplace or via API after migration.