Migrate from Simply CRM to Pipedrive

Simply CRM contacts map 1:1 to Pipedrive People. The contact's primary company link becomes the Person's primary Organization link. Owner assignment resolves by email match to a Pipedrive user. When multiple Simply CRM contacts share the same email, FlitStack preserves each as a separate Person record while linking them to the same Organization. Address, phone, and custom fields are transferred to the corresponding Person custom fields, maintaining data fidelity.

Simply CRM stores the contact's company as a named field on the contact record. This company name becomes an Organization in Pipedrive, linked to the Person via the primary organization_id. If the organization does not yet exist in Pipedrive it is created first.

Simply CRM companies map to Pipedrive Organizations. Name, domain, industry, and employee count map to Pipedrive equivalents; address, phone, and website transfer to the Organization's address and web fields. Parent-company hierarchies translate to Organization's parent_id, preserving reporting structures. Custom fields on the company become Organization-level custom fields, with their hash keys captured before import. Duplicate company names are merged into a single Organization linked to all related People and Deals.

Deals map to Pipedrive Deals. Each Simply CRM deal belongs to a pipeline with a stage; the pipeline translates to a Pipedrive Pipeline UUID, and the stage label maps to the corresponding Pipedrive stage_id. Deal amount, currency, and close date become Pipedrive value, currency_id, and close_time. Owner assignment resolves by email match to a Pipedrive user, and the primary contact links via person_id while the associated company links via org_id.

Simply CRM pipelines translate to Pipedrive Pipelines. Each Simply CRM pipeline becomes a separate Pipedrive Pipeline object. Stage labels map to Pipedrive stage IDs within each pipeline. FlitStack creates Pipelines via the REST API, retrieves stage IDs, and orders stages to match the original sequence. Probability derives from stage order in Pipedrive, and stages without a Pipedrive counterpart are flagged before deal migration.

Simply CRM activity logs (call, meeting, task, note) map to Pipedrive Activities. Call type maps to Pipedrive Activity type=call, meeting to type=meeting, task to type=task. Original timestamps and owner IDs are preserved. The activity is linked to the parent Person or Deal by ID.

Simply CRM email records migrate as Pipedrive Activities with type=email. The email body, subject, timestamp, sender, and recipient are preserved, and attachments are re-uploaded to Pipedrive Files and linked to the Activity. Each imported email is associated with a Person or Deal via the activity's person_id or deal_id. Pipedrive's email sync is a separate mechanism — imported emails remain as Activity records, not as threaded conversations in the Pipedrive inbox.

Simply CRM product catalog items (if present) map to Pipedrive Products. Unit price, SKU, description, and currency map to Pipedrive Product fields. Products are linked to Deals via the deal's product list items, and each line item records quantity and discount. When a Simply CRM deal references multiple products, all associated items are created in Pipedrive and attached to the deal.

Simply CRM custom objects require Pipedrive custom fields. Pipedrive creates custom fields per object type — a custom object that relates contacts to a custom entity becomes custom fields on Person and Deal. N:N relationships in Simply CRM need a junction approach in Pipedrive.

Simply CRM stores lead status as a field on the contact record. Pipedrive has a separate Lead object. Contacts in Simply CRM with a lead status flag are split: those actively in a sales funnel become Pipedrive Leads; closed-won or closed-lost records become People linked to Deals.

Simply CRM file attachments on contacts, companies, or deals are re-uploaded to Pipedrive Files and linked to the corresponding Person, Organization, or Deal. The original file name and any URL reference in Simply CRM are preserved in the Pipedrive file metadata. Pipedrive's 25MB per-file limit applies; files exceeding this are flagged for manual handling, and the migration log records the source location for later upload.

Simply CRM workflows and automation rules do not have a direct Pipedrive equivalent. FlitStack exports the workflow definitions as a JSON reference file that captures triggers, conditions, and actions. Rebuilding in Pipedrive's automation builder is a separate step, with effort ranging from 30 minutes for deal-stage alerts to 2 hours for multi-step sequences involving email templates and tasks. The JSON file serves as a rebuild specification for your Pipedrive admin.