Migrate from PipeRun CRM de Vendas to Microsoft Dynamics 365 Sales

PipeRun Contacts map to Dynamics 365 Contacts. The Contact-to-Company link in PipeRun resolves to the AccountId reference in Dynamics 365. We extract email, phone, job title, and custom field values from the PipeRun Contact export and map them to typed Dynamics 365 fields (emailaddress1, telephone1, jobtitle, and custom fields respectively). All contacts are imported before Accounts to satisfy the AccountId lookup dependency on insert.

PipeRun Empresa records map directly to Dynamics 365 Account. The company name becomes Account Name; the domain field maps to Website; address fields map to address1_line1, address1_city, address1_state, and address1_country. Account is the parent entity for Contact, so we import Accounts before Contacts to satisfy the AccountId foreign key.

PipeRun Deals (Negócios) are the primary revenue object and map to Dynamics 365 Opportunity. PipeRun's deal value maps to estimatedvalue; the expected close date maps to estimatedclosedate; the owner maps to OwnerId via email-based user lookup. Each Deal's assigned Funnel maps to a Dynamics 365 Record Type and Sales Process that we pre-configure during the schema design phase.

PipeRun's multiple simultaneous Funnels require mapping to Dynamics 365 Record Types. Each Funnel becomes a Record Type on Opportunity, and its stage sequence becomes a corresponding Sales Process that restricts available StageName values to the mapped stages in the correct order. Probability percentages from PipeRun stage definitions migrate to the Sales Process stage probability fields.

PipeRun Activities (calls, emails, meetings, tasks, notes) map to Dynamics 365 Activity records. Call activities map to Task with TaskSubtype = Call and CallDurationInSeconds in a custom field. Meeting activities map to Event with StartDateTime, EndDateTime, and Location preserved. Free-text notes map to Annotation records linked via ObjectId to the parent Contact, Account, or Opportunity.

PipeRun Proposals (CPQ module with ICP-Brasil e-signature) have no direct Dynamics 365 equivalent without additional licensing. We export the proposal content, line items, and total values as a written summary and a structured CSV. If the customer licenses Microsoft Dynamics 365 Sales Plus or Field Service, we map to Quote objects with the proposal PDFs attached as Note records. E-signature status and signature data cannot migrate and are flagged for manual re-execution in the destination tool.

PipeRun custom fields on Contacts, Companies, Deals, and Activities require schema pre-creation in Dynamics 365 before migration. We extract the field definitions (name, type, options for picklists) from PipeRun and create matching custom fields in Dynamics 365 via the target org's field editor or metadata API. Field types map from PipeRun (texto, número, data, dropdown, moeda) to Dynamics 365 equivalent types (nvarchar, int, datetime, picklist, money). Picklist values map with their display labels preserved.

PipeRun Users referenced as Deal owners, Activity owners, and stage assignees require mapping to Dynamics 365 User records by email. We extract all distinct owner references from PipeRun exports, match by email against the destination Dynamics 365 org's User table, and generate a mapping table. Owners without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before record import continues.

Files attached to PipeRun Deals or Proposals are downloaded from the web interface and re-associated at the destination. Files under 5 MB attach as Dynamics 365 Note records with filebody in base64. Larger files attach to SharePoint Document Libraries linked from the Account or Opportunity, with the SharePoint URL stored in a custom field on the parent record for traceability.

PipeRun tags applied to Deals and Contacts migrate to Dynamics 365 as a custom multi-select picklist field if the destination org does not have a native tagging model. The customer chooses during scoping whether to consolidate tags into a single multi-select field or split them into separate Boolean fields per tag category. Topics and TopicAssignment are available as an alternative if the customer licenses the native topic model.