Migrate from Onpipeline to Microsoft Dynamics 365 Sales

Onpipeline has no separate Lead object; all person records are Contacts regardless of qualification stage. We apply a qualification split during migration: Contacts with deal association or advanced lifecycle properties map to Salesforce-style Contact linked to an Account; Contacts with no deal association and no Company linkage map to Lead. The split rule is defined with the customer during scoping based on their Onpipeline usage patterns. We preserve the original Onpipeline contact record ID in a custom field on both Lead and Contact for traceability.

Onpipeline Companies map directly to Microsoft Dynamics 365 Sales Account. The company name, address, phone, domain, and custom fields transfer to Account. Company is created before Contact import so that AccountId can be resolved at Contact insert time, satisfying the Dynamics 365 Contact-to-Account lookup requirement.

Onpipeline Deals are the central sales record and map to Dynamics 365 Opportunity. Deal amount transfers to EstimatedValue, close date to EstimatedCloseDate, and stage to the Opportunity StageName. When an Onpipeline Deal is linked to a Company, we resolve the AccountId from the Company migration before inserting the Opportunity. Deal custom fields map to Opportunity custom fields; owner assignment resolves via email match to the Dynamics 365 User table.

Onpipeline pipeline stages (with custom names and probability percentages per pipeline) map to Microsoft Dynamics 365 Sales Processes with corresponding Stage entries. Each Onpipeline pipeline becomes a separate Sales Process, and stage probabilities round to the nearest integer percentage that Dynamics 365 accepts. The stage ordering is preserved.

Onpipeline Activities (calendar Events, Tasks, Notes) are scoped per user calendar. We migrate Events as Dynamics 365 Appointments with Start and End times, Tasks with Status and Priority preserved, and Notes as Notes linked via the Regarding field to the parent Contact, Account, or Opportunity. The owner assignment migrates by email-to-User lookup.

Onpipeline Products (name, SKU, price, stock quantity) map to Dynamics 365 Product2 records. Standard Price Book entries are created during import. Inventory levels transfer to the warehouse quantity fields if Business Central inventory management is in scope; otherwise they are stored as custom fields on Product2.

Onpipeline Quotes (header, line items, pricing, e-signature status) map to Dynamics 365 Quote. Quote PDFs and e-signed documents migrate as Note attachments on the Quote record. Quote-to-Opportunity conversion is noted as a post-migration step the admin completes manually in the Dynamics 365 UI, as the Quote status cannot be set to Won programmatically without a full sales order workflow.

Onpipeline Invoices (header, line items, payment status) map to Dynamics 365 Invoice records. Payment status carries over as InvoiceStatus. Recurring invoice configurations are noted in the migration scope document; automated recurring invoice generation requires manual configuration in Dynamics 365 or Business Central because it is tied to the Onpipeline Advanced plan feature.

Onpipeline custom fields on Contacts, Companies, Deals, and Products are extracted with their data types and mapped to equivalent Dynamics 365 custom fields. We pre-create the destination schema (custom field API names with __c suffix, field types matched to Dynamics 365 column types) and validate before import. The custom field schema document is delivered before any data migration begins.

Onpipeline Users are matched by email address against the Dynamics 365 destination User table. Owner references on Deal, Contact, and Activity records resolve through this User map. Owners without a matching Dynamics 365 User enter a reconciliation queue for the customer's admin to provision before record import resumes.