Migrate from Pipedrive to EspoCRM

Migrate from Pipedrive to EspoCRM without losing the pipeline

Moving from Pipedrive to EspoCRM is mainly a data mapping and pipeline rebuild job, followed by a short, controlled cutover. It is not a feature-for-feature swap, and the work goes better when the sales operations lead treats it that way. A renewal, a per-seat cost increase or a data residency requirement usually starts the project, but the outcome depends on how cleanly deals, stages, people, organizations and activities land in EspoCRM. Most teams have an internal administrator who owns the field mapping and the sign-off, and they bring in an implementation partner for the importer setup, the stage configuration and the cutover runbook. Effort scales with the number of custom fields, the age of the data and how many reps must be trained, so ask for a written scope that lists each object and each custom field before any work starts.

Start by exporting from Pipedrive and deciding what each source field becomes in EspoCRM. Pipedrive's Export data tab produces XLSX or CSV files for deals, people, organizations and activities, and those files remain available for a limited window, so schedule the final export with that in mind. In EspoCRM, the import step runs through the Import documentation's field mapping, so create any custom fields in the Entity Manager first and confirm that duplicate detection rules match how your team identifies people and companies. Rebuild each Pipedrive pipeline as an EspoCRM kanban view with the same stage order, and test it with a copy of real but non-sensitive records. Run at least one full trial import on a staging instance, then compare record counts and owner assignments against the source files before anyone relies on the data.

The cutover itself should be short and scripted: freeze new data entry in Pipedrive, run the final delta export, import it, check open deals and reminders, then switch users over. Plan for the risks that are easiest to miss, including linked items that need separate exports, email sync that must be reconfigured, and activities whose history is lost if they are not imported. Confirm how user accounts, teams and roles will be set up before go-live, because EspoCRM permissions decide what each rep sees. Keep the Pipedrive subscription active until the team has verified the migrated pipeline, and keep the exported files in a controlled location for your retention policy. Ask your implementation partner to document each step as an evidence record, since that record supports later compliance reviews even though it does not replace an independent audit.

Which Pipedrive capabilities map cleanly to EspoCRM and which need rework

This table compares the main Pipedrive capabilities with their closest EspoCRM equivalents and marks each as clean, needs rework or gap. Read it as a planning checklist: a clean row can usually be moved with standard import and configuration, while rework and gap rows need design time or an extension decision before cutover. Email sync, mobile use and any Pipedrive-specific add-on must be confirmed against EspoCRM's current docs and extensions before you rely on them.

Pipedrive capability	EspoCRM equivalent	Status	What to confirm or plan
Pipelines and stages	Opportunities with a stage field, shown in a kanban view	Needs rework	Rebuild each Pipedrive pipeline as a stage list and confirm the kanban layout for each sales team.
Deals	Opportunities with amount, close date, stage and owner fields	Clean	Map deal fields to opportunity fields in the import file and test a sample of closed and open deals.
People	Contacts linked to accounts	Clean	Check duplicate handling on email addresses and confirm how multiple emails per person are stored.
Organizations	Accounts with related contacts and opportunities	Clean	Map Pipedrive organization IDs to account records so relationships survive the import.
Activities and notes	Calls, meetings and tasks on the record timeline, with notes as stream posts	Needs rework	Pipedrive exports activities and notes separately, so plan a second import and confirm the link to each parent record.
Files	Attachments on records, stored on your server	Needs rework	Pipedrive file exports are separate from data exports, so confirm how files are retrieved and re-attached.
Reporting	Standard list and dashboard views, with reports available through the Advanced Pack	Needs rework	Recreate Pipedrive Insights reports and confirm whether the Advanced Pack is included in your chosen edition.
Automation	Workflows and before-save formula scripts, with BPM through the Advanced Pack	Needs rework	Rewrite Pipedrive automations as EspoCRM workflows and test each rule on a staging instance.
Email sync	To be confirmed against current EspoCRM docs and the Google and Outlook extensions	Gap	Do not assume two-way sync parity. Test mailbox connection, logging and calendar behavior before cutover.
Mobile use	To be confirmed against current EspoCRM docs and mobile access options	Gap	Test how reps use the pipeline on a phone browser and confirm whether a native app is needed.
Pipedrive-specific add-ons	Official extensions such as VoIP, Google, Outlook and Zoom, and third-party options	Gap	List every Pipedrive add-on your team uses and confirm an EspoCRM equivalent or a replacement workflow.
API access	REST API with API key, HMAC and basic authentication through dedicated API users	Needs rework	Rewrite integrations against EspoCRM endpoints, and use HMAC for the most secure access.

What data moves, through which export path, and which integrations need rebuilding

Pipedrive's documented route is the Export data tab, which produces XLSX or CSV files that stay available for a limited window. Linked items such as notes and files need their own handling, and the integrations around the CRM must be rebuilt in EspoCRM one at a time.

Deals, people and organizations

The Export data tab covers leads, deals, organizations, people, products, activities, projects, notes and files, in XLSX or CSV. Global admins and permitted users can run it, so confirm who holds that permission before the project starts. Exported files stay available for 28 days, so schedule the export, store the files in a controlled location and record row counts for each object. Deals, people and organizations form the core of the pipeline load.

Notes and files need separate handling

Notes and files appear in the export list, but they must be matched to their parent deal or person before they land in EspoCRM. Run a test export and confirm how each note and file references its parent record, because that reference decides how the match is done. Test with a small set of deals first, and check that attachments keep their names and dates. Activities follow the same pattern, so map them to the parent record in the same pass.

EspoCRM import as the load path

Use the EspoCRM import documentation as the reference for loading CSV data, and test every load against a copy of the instance before production. Map Pipedrive fields to EspoCRM fields, and map pipeline stages to statuses, in a sheet that migration and sales operations both sign off. Check how duplicate people and organizations are detected and which records link to which accounts. Keep the original exports unchanged so each load can be repeated.

Email and calendar sync

Pipedrive's email and calendar sync runs on live connections, and an export does not carry those connections over. EspoCRM offers official extensions for Google and Outlook, so reps need those connected and tested against their own mailboxes. Confirm the current extension requirements, the mail server settings and who owns each connection. Decide which historical email stays in the old mailbox and which is recorded against records in EspoCRM.

Marketing and campaign connectors

If the team sends campaigns through Campaigns by Pipedrive or another mailing tool, rebuild the contact sync before the old sync is switched off. EspoCRM lists an official MailChimp extension, so check whether it fits the sending platform in use. Take list membership and unsubscribe status from the export, because consent records control who can be emailed. Run a test send to a small internal list before the first live campaign.

Login and API consumers

EspoCRM supports OpenID Connect sign-in from version 7.3, along with LDAP, including Active Directory and OpenLDAP. Its own two-factor login is not compatible with OIDC, so decide where multi-factor enforcement lives before rollout. List every system that calls the Pipedrive API today, then create dedicated API users with narrow roles in EspoCRM. The docs describe HMAC as the most secure method and basic authentication as not recommended.

How the migration runs from inventory to decommission

The sequence moves Pipedrive deals, people, organizations and activities into a self-hosted EspoCRM instance in controlled stages, so each stage has a checkpoint before the next one starts. Sales reps keep working in Pipedrive until the cutover is agreed in writing.

Inventory pipelines, fields and users
Start by listing every pipeline and stage, every custom field on deals, people, organizations and activities, and every user with their role and visibility. Confirm the list with the sales lead and an admin who can open the Pipedrive settings. The output is a signed-off inventory sheet that names each stage, each custom field and its type, and each user who needs an EspoCRM login. You know this step is done when no pipeline or field is referenced in a live report without an owner.
Build a pilot instance with sample deals
Install EspoCRM on a staging server you control, following the EspoCRM installation documentation for your operating system and database. Load a sample of real deals, people, organizations and activities from a recent export, covering each stage and at least one custom field of every type. The output is a working pilot where you can open a deal, see its stage in the kanban view, and check that linked people and organizations resolve correctly. You know this step is done when a sales lead signs off on the sample records.
Map fields and set up EspoCRM entities
Create a field mapping document that pairs each Pipedrive field, stage and user with its EspoCRM entity, field and team. Configure custom fields and pipeline stages in the Entity Manager, then decide how Pipedrive activities and notes will be imported, since they usually come from separate exports. The output is a mapping sheet with a column for transformation rules, such as how dates, currency values and multi-select fields are converted. You know this step is done when every source field has a target or an explicit decision to drop it.
Import the full export into staging
Export the data from Pipedrive as XLSX or CSV, then use EspoCRM's import tool, described in its import documentation, to load each entity in dependency order: organizations and people first, then deals and activities. Keep the original export files unchanged and log every import run. The output is a staging instance with import logs that show the record counts and any rows that failed. You know this step is done when each entity's counts match the export and every failed row has a recorded fix.
Run both systems in parallel
For an agreed period, reps keep updating Pipedrive while a small group uses EspoCRM on the same deals, and admins compare pipeline totals, stage counts and open activities between the two systems. Any discrepancy is traced back to the mapping sheet and corrected in the import rules, then the import is rerun on staging. The output is a reconciliation log and a list of resolved gaps. You know this step is done when the reconciliation shows no unexplained differences for two consecutive checks.
Cut over users and data
Freeze edits in Pipedrive, run a final export, import only the changes since the last load, and switch users to EspoCRM with their accounts and permissions tested in advance. If you plan to use an identity provider, confirm the OIDC or LDAP sign-in before go-live. The output is a production EspoCRM instance holding current data and a written cutover record that lists the export timestamp and who approved the switch. You know this step is done when each rep can open their pipeline and see the expected deals.
Archive exports and decommission Pipedrive
Keep the final Pipedrive exports and the import logs in your own archive, because Pipedrive makes exported files available for only a limited window. Record which Pipedrive files, integrations and API tokens are removed, then cancel the subscription once your contract terms allow it. The output is an archive index with checksums and a decommission record signed by the data owner. You know this step is done when the archive can be opened, and the Pipedrive account no longer holds live data your team needs.

How EspoCRM is hosted and what the self-hosted stack needs

The first decision is where EspoCRM will run, and the documented server configuration sets the boundaries. EspoCRM runs on PHP 8.3 to 8.5 with MySQL 8.0 or newer, MariaDB 10.6 or newer, or PostgreSQL 15, served by Apache, Nginx or IIS. Your infrastructure team should check these versions against the operating system packages and the database patch levels they already support, because a supported PHP version and a supported database engine are the usual points where an otherwise simple install stalls. Confirm also whether your standard web server and database licensing and support contracts cover the chosen combination.

For a small team with no existing stack, the installation script is the quickest documented path. It targets Ubuntu, Debian and Linux Mint and deploys a Docker-based stack with Nginx and MariaDB, with optional Let's Encrypt certificates. The same script's command.sh utility handles backups, restores and upgrades. Treat the Docker stack as a starting point to review, not a finished production design: your team should decide where backups are stored, how they are encrypted, how often restores are tested, and who approves an upgrade. Ask the vendor or DeployOpen to walk through the command.sh restore path on a copy of the data before cutover, since a backup that has never been restored is not yet a backup.

Background jobs, such as scheduled tasks and queued processing, depend on a cron entry or scheduled task on the host. If that job does not run, reminders, some workflows and other deferred work will quietly stop, so add a monitor that alerts when the job has not run. Also confirm your network model before go-live: decide whether EspoCRM sits behind a reverse proxy, how TLS is terminated, and whether it is reachable only from the corporate network or from remote laptops. Infrastructure teams in regulated environments should record these answers as part of the hosting design, because they become the first questions in any later security or compliance review.

What drives migration cost and duration, and how to keep each down

This table lists the factors that change the cost and effort of moving from Pipedrive to EspoCRM, and what to do about each one. Read it before requesting a written scope, since the drivers are mostly known from your own Pipedrive export and team structure. One-time work (mapping, import, training, workflow rebuild) is separate from recurring work (hosting, backups, upgrades, support).

Driver	Why it moves cost or effort	How to keep it down
Record volume	More deals, people, organizations and activities mean longer exports, larger import runs and more verification. Pipedrive exported files are only available for 28 days, so the export window is fixed.	Export in batches by pipeline or year, run a test import on a sample, and confirm the export is complete before the source account is reduced.
Custom fields and pipelines	Each custom field needs a matching EspoCRM field, and each pipeline needs a stage mapping. Odd field types and many pipelines add mapping and testing time.	Audit fields before export, retire unused ones, and map each remaining field to an EspoCRM field type once in a shared spreadsheet.
Data quality in Pipedrive	Duplicate people, orphaned activities and inconsistent stage names need cleanup before import, and errors surface later as wrong reports.	Deduplicate and standardize stage names in Pipedrive first, and agree on a record owner rule for each entity.
Users, teams and roles	Each user, team and permission set must be created in EspoCRM and tested against the sales, management and admin roles reps actually use.	Model roles from a short list of job functions, and test visibility with two or three real reps before cutover.
Integrations to rebuild	Email sync, calendar, telephony, marketing and any custom API scripts connected to Pipedrive must be rebuilt or replaced, and each one needs its own test.	List every connected tool before the project starts, mark which are essential at cutover, and use EspoCRM's official extensions where they match.
Advanced Pack workflow and reporting needs	Reports, workflows and Business Process Management come with the Advanced Pack in EspoCRM Cloud plans, and self-hosted use may require the add-on, so confirm licensing before you design automation.	Start with the pipeline reports and stage-change automations reps rely on, and defer rarely used workflows to a second phase.
SSO and identity setup	OpenID Connect or LDAP configuration, group-to-team mapping and testing with your identity provider add work. EspoCRM's own 2FA is not compatible with OIDC, so the login plan affects policy design.	Confirm the identity provider and group structure early, and reuse your existing directory groups rather than creating EspoCRM-only accounts.
Hosting and backup setup (recurring)	The server, database, PHP runtime, cron for background jobs, TLS certificates and backup schedule all recur as infrastructure and operations work. The installation script can deploy a Docker-based stack with Nginx and MariaDB, but production hardening is still separate.	Choose a supported database version from the EspoCRM server configuration docs, test restores, and agree on monitoring and patch windows in the written scope.
Training and change management (one-time)	Reps need to learn the kanban pipeline and activity logging in EspoCRM, and managers need new reports. Training time grows with user count and the number of workflows changed.	Train on a sandbox copy built from real data, and keep a one-page guide for the stage and activity habits you want kept.
Upgrades and support (recurring)	EspoCRM releases move between major and minor versions, and extensions must be checked after each upgrade. Support needs grow with the number of custom workflows.	Pin a version, test upgrades in a staging copy, and ask any provider for a written upgrade and support scope before signing.

How the migration differs by team size and starting point

A team with one pipeline, a short list of stages and few custom fields usually has the smallest migration. The main work is mapping a handful of fields, loading deals, people and organizations from Pipedrive's export files, and confirming that the kanban board in EspoCRM shows the same stages in the same order. Because the data set is small, one trial import into a staging instance is often enough to find mapping errors before the real load.

Scope: Deals, people, organizations and a single pipeline, with stages mapped to EspoCRM's status values.
Sequencing: Build the stage configuration and fields first, then import organizations, people and deals in that order so links resolve.
Testing: Import once into staging, open a sample of deals from each stage and compare values field by field.
Activities: Decide whether historical activities matter for this team. Many small teams carry only open tasks forward.
Hosting: A single-server deployment using the installation script may be enough, but confirm backup and restore steps with your own team.

Before cutover, ask a sales rep to run one full deal from first contact to close in the new system and confirm nothing is missing.",

What usually goes wrong in a Pipedrive to EspoCRM move, and how to prevent it

Most failed Pipedrive to EspoCRM moves fail on data that never made it across, not on the import itself. The risks below share one root cause: the export is treated as a complete copy when it is only a set of flat files. Each card names the failure and the check that catches it before cutover.

Lost activity history

Pipedrive's Export data tab covers leads, deals, organizations, people, products, activities, projects, notes and files, but linked items such as notes and files need their own exports. Activities imported without their deal links appear as orphaned records, and reps lose the call and meeting trail behind each deal. Before cutover, sample ten deals with long histories and confirm each activity, note and file is reachable from the matching EspoCRM record.

Stage mismatches that break reporting

Pipedrive pipelines and EspoCRM statuses rarely line up one to one, so a stage renamed or merged during import shifts deal counts in every forecast report. Build a stage map on paper first, listing each Pipedrive stage, its EspoCRM status and the probability each one carries. Then run one pipeline report in both systems and reconcile totals by stage before users see the data.

Duplicate people and organizations

Exports from several Pipedrive accounts or years of manual entry often contain the same contact under slightly different names or email addresses. Importing them unchanged doubles contact counts, splits deal history between records and triggers duplicate outreach. Deduplicate on email address and organization domain in the spreadsheet before import, and keep a mapping file of old Pipedrive IDs to new EspoCRM IDs for later reference.

Unowned records after user mapping

Records keep the owner ID from Pipedrive, and if a departed rep or a mistyped user has no matching EspoCRM account, the deal lands with no owner and drops out of rep dashboards and assignment rules. Create every EspoCRM user and assign teams before the import runs, then count records per owner after load. Any owner with zero matches or unexpected totals needs a reassignment decision before go-live.

Email sync gaps at cutover

Email threads linked to Pipedrive deals do not move with a CSV or XLSX export, so reps who expect their inbox history inside EspoCRM find blank timelines. Mailbox connection must also be configured per user, and any gap between the last Pipedrive sync and the first EspoCRM sync can leave messages unlinked. Decide whether historical email is archived elsewhere, and test sync with two pilot reps for several days before switching everyone over.

Integrations that silently stop

Zapier flows, webhooks, API scripts and reporting connectors that point at Pipedrive keep working until the account closes, then fail without a clear alert. Inventory every integration and its owner before cutover, and map each one to an EspoCRM API user with the narrowest role that works. The EspoCRM API supports HMAC, which the docs describe as the most secure method, so prefer it over basic authentication, which is not recommended.

Export files that expire

Pipedrive exported files remain available for 28 days, so an export pulled early and imported weeks later may be gone and must be regenerated. Date-stamp each file, record the export time and the Pipedrive account used, and re-run exports within the last week before the final cutover. Keep a copy of every file in your own secured storage, not only on a laptop.

Backups that were never tested

A nightly backup of the EspoCRM database and file storage proves little until someone restores it onto a separate server and opens real records. Because EspoCRM relies on cron for background jobs, a restored instance also needs its scheduled tasks rechecked. Schedule a restore test on a staging host before cutover, confirm attachments and custom fields return, and record the time the restore took so the recovery plan reflects real results.

What buyers ask before moving from Pipedrive to EspoCRM

What drives the cost of moving from Pipedrive to EspoCRM?

The cost is driven by the work around the software, not the license, because the open-source edition is free to download and self-host. The main components are hosting infrastructure, the implementation work (installing EspoCRM, mapping Pipedrive fields to EspoCRM entities, importing deals, people, organizations and activities), any extensions your reps need, backups, upgrades and support staff time. Hosting and upkeep recur every year, while mapping and import are largely one-time. Costs rise with the number of custom fields, the volume of linked records, the number of integrations (email, calendar, phone) and how many workflows you rebuild. When you ask for a quote, request a line-by-line breakdown of setup, migration, extensions, hosting and support, and confirm which of these your own staff will carry out.

How long does a Pipedrive to EspoCRM migration usually take?

The duration depends on how much data and configuration you move, and no fixed timeline applies to every team. Timing is shaped by the number of pipelines and stages, the volume of deals, people and organizations, how many activities and notes need to follow their parent records, how many custom fields exist, and whether email or calendar sync must be rebuilt. A small team with a single pipeline and clean data will move far faster than a team with several pipelines, years of history and heavy customization. Ask any implementation partner for a written scope with milestones, and plan a parallel test import before the cutover date.

What does our internal team need to provide for the migration?

Your team needs to supply decisions and data knowledge that no tool can infer. A sales operations owner should define the pipeline stages, required fields and deal ownership rules. An administrator should confirm which Pipedrive exports contain the records you need, since Pipedrive's Export data tab covers leads, deals, organizations, people, products, activities, projects, notes and files as XLSX or CSV, and exported files remain available for 28 days. Someone must also own the hosting environment, the identity source for logins and the decision about which historical records to keep. Reps should test their own pipelines in the staging instance before go-live.

Can we migrate from Pipedrive to EspoCRM without outside help?

Yes, a technically capable team can do this in-house, provided it has someone comfortable with a PHP application stack, a MySQL 8.0+, MariaDB 10.6+ or PostgreSQL 15+ database, and the CSV import process. EspoCRM publishes an installation script for Ubuntu, Debian and Linux Mint that deploys a Docker-based stack with Nginx and MariaDB, plus a command.sh utility for backups, restores and upgrades. The hard parts are usually mapping and validating data, rebuilding automation and keeping the server patched. If your team lacks that capacity, DeployOpen can plan, implement and document the migration under a fixed-scope written agreement, and retainers are available for later upgrades and support.

How does EspoCRM Cloud pricing compare with self-hosting?

EspoCRM Cloud is priced per user, and the EspoCRM pricing page lists 15 US dollars per user per month on the Basic plan (minimum 3 users), 25 dollars on Enterprise (minimum 5 users) and 69 dollars on Ultimate (minimum 10 users), with the Advanced Pack included in all cloud plans. Self-hosting removes the per-user subscription but adds server, backup, monitoring and administration costs that you pay for directly or through a partner. For a given team size, multiply the cloud rate by seats and months, then compare that total with your infrastructure and support estimates over the same period. Confirm whether you need cloud features such as hosted backups, and whether your data residency rules allow a hosted service at all.

What happens to our data after cutover from Pipedrive?

After cutover, your records live in the EspoCRM database on infrastructure you control, and Pipedrive becomes a source you can retire once you have verified the import. Keep the original Pipedrive exports in an archive with clear retention rules, because Pipedrive's exported files are only available for 28 days. Confirm record counts and spot-check deals, contacts and activities against the source, and decide how long to keep the old Pipedrive account read-only. Backups of the EspoCRM database and files should be tested with a restore, and retention and deletion policies should be written down before the team starts using the new system.

Which EspoCRM features do reps lose compared with Pipedrive?

Reps should expect a different setup for pipeline views and automation rather than a like-for-like copy of Pipedrive. EspoCRM provides a kanban view for pipelines, but the exact screens, mobile experience and email features need to be tested with your own reps before you commit. Automation in EspoCRM uses Formula Script in before-save scripts, workflows and Business Process Management, and reports and BPM sit in the Advanced Pack, which is an official add-on included in all EspoCRM Cloud plans. For a self-hosted install, confirm with the EspoCRM documentation and the extension list which official extensions your team needs, and budget time to rebuild any Pipedrive automations that reps rely on daily.

How should we handle sign-in and security on self-hosted EspoCRM?

Plan sign-in before users are imported, because it affects how accounts are created and how access is revoked. EspoCRM supports OpenID Connect sign-in since version 7.3, with optional user creation on first login, mapping of identity provider groups to teams, backchannel logout and a fallback login method, and it also documents LDAP authentication including Active Directory and OpenLDAP. EspoCRM's own two-factor authentication is not compatible with OIDC, so confirm how your identity provider handles multi-factor checks. For API access, the documentation describes HMAC as the most secure option and basic authentication as not recommended, so use dedicated API users with role-based permissions for integrations.

How DeployOpen scopes and runs a Pipedrive to EspoCRM migration

DeployOpen is a Chainscore Labs company that plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For a Pipedrive to EspoCRM move, that means the EspoCRM server, its database, the network path to your sales users and any identity integration run in your cloud account, data center or air-gapped network. Most engagements are fixed-scope, so the written scope should name the Pipedrive exports in use (deals, people, organizations, activities, notes and files), the EspoCRM stages and kanban views to rebuild, the user roles and teams, and the extensions to install. Confirm early whether your Pipedrive export covers the linked items you need, because the export window and visibility rules on the Pipedrive side affect how much work the migration involves.

A quote follows from that written scope, so the reader should expect the proposal to itemize the components: discovery and data mapping, EspoCRM installation and hardening, import testing, pipeline rebuild, user acceptance testing, cutover and documentation. Ask for each item to be tied to a deliverable and a named acceptance check, such as record counts reconciled against the source export or a rep signing off on a test pipeline. Ask also whether the proposal includes the decisions on authentication. If you plan to use OpenID Connect or LDAP sign-in, the scope should say which identity provider, which group-to-team mapping and which fallback login method are in place, since EspoCRM's own two-factor authentication is not compatible with OIDC.

Ongoing work after cutover is covered by a retainer rather than the fixed project. Retainers can include patching and upgrades, backup verification, user administration and continuous security testing, which is useful because EspoCRM's background jobs depend on cron or a scheduled task and an upgrade cycle needs a plan. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. If your organization needs formal assurance over the CRM, the scope should list the evidence DeployOpen will produce and the independent auditor or certification body you will engage separately.

Migrate from Pipedrive to EspoCRM