Skip to content

Integrations

CRM Migration

Move from Salesforce, HubSpot, Zoho or Pipedrive — accounts, contacts, deals and history — with guided field mapping and no cutover weekend.

CSV Import Back to Integrations

Migrate from your CRM

Muntri connects to your existing CRM, pulls the records you choose, and maps each field onto its own model. Everything lands as a validated record on the single shared timeline — properly numbered, deduplicated and linked.

  • Salesforce

  • HubSpot

  • Zoho CRM

  • Pipedrive

What comes over

From your CRM Into Muntri
Companies / accounts Accounts
People / leads Leads & contacts
Deals / opportunities Opportunities
Associated activity & history Timeline activity

You choose which object types to bring, so you can start small (accounts and contacts) and add opportunities later.

The migration flow

Create a migration. Pick your source CRM.

Connect. Authorize Muntri against the source — it verifies the connection before proceeding.

Map fields. Match your CRM's fields to Muntri's. Sensible defaults are suggested; adjust as needed.

Choose how to handle conflicts. Skip, overwrite or merge when a matching record already exists.

Run & watch. The migration pulls records in the background — track total, processed and any errors to completion.

flowchart LR
  A[Pick source CRM] --> B[Connect]
  B --> C[Map fields]
  C --> D{Conflict?}
  D -->|match found| E[Skip / Overwrite / Merge]
  D -->|new| F[Create]
  E --> G[Records live]
  F --> G
  classDef n fill:#ffffff,stroke:#2563eb,stroke-width:1.5px,color:#0B1024;
  class A,B,C,D,E,F,G n;

Field mapping

You control exactly how source fields land in Muntri. Map each column, and Muntri handles the rest — assigning record numbers, validating relationships (an opportunity needs its account first) and enforcing value constraints.

Deduplication is built in

Muntri matches incoming records against existing ones by email and name, so a migration merges into what you already have instead of doubling it up.

Conflict handling

When an imported record matches one that already exists, you decide what happens:

Mode Behaviour
Skip Keep the existing record; ignore the incoming one
Overwrite Replace the existing record with the imported data
Merge Fill in only the empty fields from the imported data

Every record arrives clean

  • Proper numbering — sequence numbers assigned to every record.

  • Relationships validated — accounts exist before their opportunities.

  • Constraints enforced — no negative amounts, no broken links.

  • Source tracked — migrated records are tagged, so their origin is always clear.

Just a spreadsheet?

If you only need to load rows from a file rather than connect a live CRM, use CSV Import.