Migrate from Manta Business Management Software to Pipedrive

Manta BMS Contact records map to Pipedrive Person. We map standard fields including name, email address, phone number, and physical address to their Pipedrive equivalents (name, email, phone, address fields). Any Manta contact records with no email address are flagged for deduplication review before import because Pipedrive uses email as the primary dedupe key. Contact-company linkage migrates by resolving the company name to the corresponding Pipedrive Organization record created in the same migration run.

Manta BMS Company records map to Pipedrive Organization. We preserve company name, industry classification, employee count, and website URL where these fields exist in the export. Pipedrive Organization supports a clean URL field; we populate it from Manta's website value. Organizations are imported before Persons so that the organization_id reference on each Person record is satisfied at the moment of insert, avoiding orphaned organization lookups.

Manta BMS Lead records map to Pipedrive Lead. We map lead source, status, assigned owner email, and creation timestamp. Pipedrive Lead uses a separate Lead object distinct from Person, so Manta leads that represent unqualified prospects import directly without requiring the Lead-to-Contact conversion step that applies in some other CRM migrations. Owner resolution runs by email match against Pipedrive Users provisioned before migration.

Manta BMS Deal records map to Pipedrive Deal. We map deal title, monetary value, expected close date, and stage. Pipeline and stage names from Manta require mapping to Pipedrive's pipeline configuration, which we set up in Pipedrive before the deal import begins. Deals without a linked person or organization are imported as standalone deals and flagged for the customer to link post-migration if the association data is recoverable from the Manta export.

Manta deal stages are read from the export and mapped to Pipedrive stages within the customer's target pipeline. We create a Pipedrive pipeline before deal import that mirrors the stage sequence from Manta, preserving stage names and approximate probability percentages where those values are present in the export. The pipeline configuration is a destination-side setup step that happens before any record import.

Manta BMS Activity records map to Pipedrive Activity types. We map the activity type, subject, description, due date, completion status, and timestamp. Activity-person or activity-company linkage is resolved via email match or company name lookup against the migrated Person and Organization records. If the Manta export does not include a linked person or company reference for activities, we import them as standalone activities and note the limitation in the migration report.

Manta BMS user records map to Pipedrive Users. We resolve by email address match against the Pipedrive destination account's user list. Any Manta owner that does not have a corresponding Pipedrive User is held in a reconciliation queue and reported to the customer before production migration begins. Inactive Manta users are migrated as inactive Pipedrive Users to preserve historical assignment without granting active login access.

Manta BMS supports custom fields on contact and deal records, but these field definitions are not exposed via any documented export format or API. We do not migrate custom fields because we cannot reliably identify, extract, or remap them. We inventory all visible custom field labels during scoping and report them in the migration handoff document so the customer's Pipedrive admin can recreate them as Pipedrive custom fields and manually transfer values if desired. This is a known data gap that requires manual post-migration remediation.

Manta BMS does not expose a documented file storage access point or export endpoint for binary attachments. We do not migrate attachments or document files. If attachments are critical, the customer should export them manually from Manta and re-attach them in Pipedrive post-migration. We document this limitation in the scoping report before migration begins.

Manta BMS tag data, if present in the export as a comma-separated field or multi-select list, maps to Pipedrive Person or Organization labels. We parse the tag values during data transformation and insert them as Pipedrive label records linked to the corresponding Person or Organization. The customer confirms during scoping whether tag-based segmentation is relied upon for reporting, since Pipedrive labels function differently from Manta's internal tag taxonomy.