---
title: "Migration"
description: " How to migrate your documentation from an existing Markdown solution to Docus"
canonical_url: "https://docus.dev/en/getting-started/migration"
---
# Migration

> How to migrate your documentation from an existing Markdown solution to Docus

## **Migrating from Docus v3 to v4**

Docus v4 introduces a new **layer-based approach** that leverages the official Nuxt CLI instead of the custom Docus CLI. While your existing content and configuration remain compatible, you'll need to update your commands and project setup.

### **⚠️ Breaking Changes**

The main breaking changes are related to CLI commands:

<table>
<thead>
  <tr>
    <th>
      v3
    </th>
    
    <th>
      v4
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        npx docus init my-docs
      </code>
    </td>
    
    <td>
      <code>
        npx create-docus my-docs
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        docus dev
      </code>
    </td>
    
    <td>
      <code>
        nuxt dev --extends docus
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        docus build
      </code>
    </td>
    
    <td>
      <code>
        nuxt build --extends docus
      </code>
    </td>
  </tr>
</tbody>
</table>

<tip>

Your existing Markdown content and MDC syntax will work without changes. The migration primarily involves updating your development and build workflow.

</tip>

## **Migrating to Docus**

Already using a Markdown-based solution for your documentation? Whether it’s **Docus v1**, the **Nuxt UI docs template**, or another static site setup, migrating to Docus is simple and straightforward.

Docus offers a clean and maintainable solution with a single dependency: the Docus library itself. There’s no need to manage multiple dependencies. With everything built-in and maintained together, keeping your documentation up to date is easier than ever.

To migrate, just move your existing Markdown files into the `content/` directory of the Docus starter.

From there, you have two scenarios:

- **If your current docs already use Nuxt Content and the MDC syntax**, make sure the components used in your content exist in Nuxt UI. If any components are missing, you can easily create your own custom ones.
- **If you’re using standard Markdown**, you can copy your files as is. Then, enhance your documentation progressively using the [built-in components](https://docus.dev/en/essentials/components) provided by Nuxt UI.

Once your content has been moved to the `content/` folder, you can go through the [configuration section](https://docus.dev/en/concepts/configuration) to easily customize your app.

Docus is designed to focus on writing content, so if you're already using Markdown, you can easily switch to it.


## Sitemap

See the full [sitemap](https://docus.dev/sitemap.md) for all pages.