Migrate from Basic Online CRM to Pipedrive

Basic Online CRM Contact records map 1:1 to Pipedrive Person. We map name fields (first_name, last_name), email, phone, and address fields to their Pipedrive equivalents. Any non-standard fields migrate as custom Person fields, and we ask the customer to confirm intended data types before schema creation in Pipedrive because Basic Online CRM exports all custom fields as plain strings.

Basic Online CRM Companies map to Pipedrive Organizations by name match. The schema is flat on both sides with no subsidiary hierarchy. We flag duplicate organization names (same string appearing multiple times) during scoping and ask the customer to de-dupe or confirm before import. Organization is created before Person so that the org_id lookup on Person is satisfied at insert time.

Basic Online CRM Deals map to Pipedrive Deals with stage, value, currency, and expected close date preserved. The critical step is resolving the linked Person and Organization. Basic Online CRM exports Deals with a contact_id field containing a numeric internal ID, not an email or name. We request a dual export of Contacts and Deals, cross-reference the IDs against the contact list to retrieve names, and write the resolved Person name as the deal Person link in Pipedrive. Any Deal referencing a deleted Contact is flagged as orphaned for customer resolution.

Basic Online CRM Notes are free-text entries with no type, timestamp, or assignee metadata beyond what was explicitly set. We migrate them as Pipedrive Activity records with type=note, preserving the body text. Timestamps migrate if present in the export; untimestamped notes receive the import date. Notes without a linked Deal, Person, or Organization are attached to the most recently created or most relevant record based on context in the note body.

If the Basic Online CRM instance contains task records, they are simple title-and-status items with no due-date enforcement or assignee. We migrate them as Pipedrive Activity records with type=task, using the title as subject and the status as completion state. Pipedrive requires an owner_id on Activities, so we resolve the owner by email match against the Pipedrive User table or apply the customer-designated default owner if no explicit owner is present in the source data.

All Basic Online CRM custom fields export as untyped strings regardless of their intended type. We stage the raw export, identify fields that look like dates (format detection), numbers, or drop-down values, and propose a Pipedrive field type for each. Date fields in particular may appear as 'Jan 15 2024' in one export and '15/01/2024' in another; we standardise these to ISO 8601 (YYYY-MM-DD) during the transform phase. The customer reviews and approves the type mapping before Pipedrive schema creation and import.

Basic Online CRM does not surface record-level owner assignment in its exports. We ask the customer during discovery which Pipedrive User should own migrated records, and we apply bulk owner assignment during the write-back phase. If multiple Basic Online CRM users are present in the source data, we extract their names and ask the customer to map each to a corresponding Pipedrive User by email.

Basic Online CRM does not host or store file attachments natively. Any files referenced in Notes or Deal descriptions must be sourced externally by the customer and re-uploaded to Pipedrive after migration. We include a pre-migration checklist item asking customers to identify any such files and the records they are associated with.

Basic Online CRM does not offer workflow automation on any tier below Enterprise, and Enterprise API access is undocumented. There are no automation rules to migrate regardless of tier. Pipedrive Automation Studio (Advanced tier and above) must be rebuilt by the customer's admin post-migration. We deliver a written inventory of any automated behaviours the customer wishes to recreate in Pipedrive.

Basic Online CRM user seats (from the Free, Starter, or Professional tier) map to Pipedrive user accounts. We extract the list of active Basic Online CRM users from the platform settings and map them to Pipedrive Users by email. The customer provisions the corresponding Pipedrive users before migration so that OwnerId references resolve during write-back.