Migrate from noCRM.io to Pipedrive

noCRM's Lead object is the primary record and contains both contact details and company information within a single entity. During migration we split each Lead into a Pipedrive Person record (for name, email, phone, and social URLs) and an Organization record (for company name, domain, address, and industry). The split is executed by parsing the noCRM Lead's company field and creating or matching an Organization first, then linking the Person to it via the org_id field. If no company information exists in noCRM, the Person is created without an Organization link. We preserve all noCRM Lead custom Predefined Fields by mapping them to Pipedrive Person or Organization custom fields, creating each destination field with the matching data type before import begins.

noCRM Lead statuses (Won, Lost, Cancelled, To-Do, Standby) do not map directly to any Pipedrive standard field. We use the status to determine Deal creation: Leads with status Won or Lost generate Pipedrive Deals with the corresponding stage. To-Do and Standby Leads generate open Deals in an early stage. Cancelled Leads can be archived or imported as Deals in a Cancelled stage depending on the customer's reporting preference. We configure this logic in the transformation layer before migration so that no Deals are created from Cancelled or Lost Leads unless explicitly requested.

Each noCRM Pipeline contains ordered Steps that represent sales process stages. We map these to Pipedrive Pipeline Stages by preserving the step order and probability. On Starter noCRM accounts, only one Pipeline exists and it maps to one Pipedrive Pipeline. On Expert or Dream accounts with multiple Pipelines, we create multiple Pipedrive Pipelines and map each noCRM Step to the corresponding Pipedrive Stage within its parent Pipeline. Stage probability percentages are extracted from noCRM statistics if available, otherwise set as defaults and flagged for the customer's admin to adjust post-migration.

noCRM Tags are freeform labels applied to Leads for categorization such as industry, source, or priority. We preserve all tags and map them to Pipedrive Labels attached to the Person record. Tags with a many-to-many relationship to Leads are exploded into individual Label assignments on each migrated Person. If a noCRM tag contains characters not supported in Pipedrive Labels, we sanitize the label text and document the change in the mapping workbook. Labels do not carry forward to Deals or Organizations unless the customer requests a cross-object labeling strategy during scoping.

noCRM Prospecting Lists group Leads for outbound campaigns and reporting. We export the list membership (which Leads belong to which lists) and map it to Pipedrive Lists. Each Prospecting List becomes a Pipedrive List with the same name, and we create ListPerson records linking each migrated Person to the corresponding list. Pipedrive Lists are static by default; if the customer uses Prospecting Lists for dynamic segmentation, we document the filter criteria and recommend Pipedrive's Smart Lists feature (Marketing Engine add-on) as the equivalent rebuild target.

noCRM Lead activity logs contain chronological entries including comments, status changes, step transitions, and manual notes. We parse each log entry and map it to the appropriate Pipedrive Activity type: text comments become Notes linked to the Person; calls become Calls with duration preserved; status change entries become closed Tasks with a note describing the transition. Each activity inherits the original timestamp from noCRM. Activities with no specific type default to Pipedrive Notes attached to the Person record. We preserve the full activity chain in sequence order so that the migrated Person timeline mirrors the original noCRM Lead timeline.

Files attached to noCRM Leads (documents, images, PDFs) are exported as binary blobs alongside the lead record. We map each attachment to a Pipedrive File linked to the corresponding Person record. The original file name and MIME type are preserved. If a file cannot be retrieved from noCRM's export (due to attachment storage limits or access restrictions), we flag the missing file in the reconciliation report with the original Lead reference so the customer can locate and re-upload manually.

noCRM Users are assigned as owners of Leads and Pipelines. We map User accounts by email match to Pipedrive User records. If a noCRM User has no matching Pipedrive User, the Lead or Deal is held in an owner reconciliation queue until the customer's Pipedrive admin provisions the account. Role and permission structures (admin vs standard user) do not transfer directly because Pipedrive's permission model is administered separately in Settings > Users and permissions. We deliver a written note of the noCRM role assignments so the admin can reconfigure permissions post-migration.

noCRM Predefined Fields are custom fields configured under Admin > Sales process > Predefined Fields and vary per account. We extract the field definitions (name, data type, picklist values if applicable) and create equivalent Pipedrive custom fields on the Person or Organization object before import. Field types map as follows: text fields become Pipedrive varchar type, numeric fields become numeric type, date fields become date type, and picklist fields become set type with the same options. We check noCRM field labels for special characters or non-standard naming that could cause export issues and document any fields requiring label correction in noCRM before export.

noCRM exports aggregate performance reports covering team activity, forecast data, and lead performance per Prospecting List. These are structured Excel or JSON exports rather than native CRM objects. We deliver the raw export files alongside the migrated records so the customer can reference the historical numbers in Pipedrive Reports or a connected BI tool. Pipedrive's native reporting rebuild is outside migration scope; we document the noCRM report names, filters, and metrics so the customer's admin or a Pipedrive partner can reconstruct equivalent dashboards.

Custom Actions are account-specific menu items on noCRM Lead cards that trigger workflows such as adding won leads to an invoicing system or triggering external webhooks. These have no standard schema and no equivalent in Pipedrive's data model. We document each Custom Action's name, trigger condition, and target destination in the mapping workbook and recommend rebuild options: Pipedrive Automation rules for simple triggers, Make/Zapier for external system calls, or a custom Pipedrive Webhook for API-based integrations. The customer reviews this inventory and prioritizes which actions to rebuild post-migration.