> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# CRM standalone migration guide

> New CRM migration guide for moving from the standalone plugin-crm deployment to the integrated CRM component in Midaz v3.5.0 and Helm Chart v5.x.

<Badge stroke icon="calendar-days" iconType="regular">March 9, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams moving from standalone CRM plugin deployment to the CRM component embedded in Midaz.

This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.

## What changed

***

A new [migration guide](/en/midaz/crm/crm-migration-guide) was published to help teams transition from the standalone `plugin-crm` deployment to the integrated CRM component in Midaz.

Starting with **Midaz v3.5.0** and **Helm Chart v5.x**, CRM is no longer deployed as a separate plugin. It is now embedded directly into the Midaz monorepo and Helm chart.

### What the guide covers

***

### Architecture comparison

A side-by-side comparison of the standalone plugin architecture (separate repository, independent release cycle, dedicated Helm chart in `midaz-plugins` namespace) versus the integrated component (monorepo under `components/crm/`, single Helm chart, shared namespace).

### Step-by-step migration

The guide walks through the complete migration process:

1. **Pre-migration assessment** — Verify current plugin version and data state
2. **Configuration mapping** — How standalone Helm values translate to the integrated chart
3. **Data continuity** — Ensuring existing CRM data carries over without loss
4. **Cutover procedure** — Steps to switch from standalone to integrated deployment
5. **Validation** — Confirming the migration completed successfully

### Rollback procedure

If issues arise during migration, the guide includes a rollback procedure to restore the standalone deployment.

### Troubleshooting

Common migration issues and their resolutions, including namespace conflicts, configuration mismatches, and data access problems.

<Info>
  New Midaz deployments (v5.x+) do not need this guide. CRM is enabled directly in the Helm values as described in the [Midaz installation guide](/en/platform/helm/midaz/midaz-installation).
</Info>

### Navigation update

***

CRM is now listed as a native Midaz module in the documentation navigation, rather than under the plugins section. The CRM overview page was updated to reflect its integrated status.

This guide is available in English, Portuguese, and Spanish.

## Impact

***

This is a documentation update. Existing integrations do not need a migration from this release note alone.

## What you need to do

***

<Steps>
  <Step>
    Review the CRM migration guide before planning CRM deployment changes.
  </Step>
</Steps>

### Deadline

None.

### Why

The guide documents how to move from standalone CRM to the current Midaz-native CRM component.