---
title: "migrate"
---
## cloudquery migrate

Update schema of your destinations based on the latest changes in sources from your configuration

### Synopsis

Update schema of your destinations based on the latest changes in sources from your configuration

```
cloudquery migrate [files or directories] [flags]
```

### Examples

```
# Run migration for plugins specified in directory
cloudquery migrate ./directory
# Run migration for plugins specified in directory and config files
cloudquery migrate ./directory ./aws.yml ./pg.yml

```

### Options

```
  -h, --help             help for migrate
      --license string   set offline license file
```

### Options inherited from parent commands

```
      --cq-dir string            directory to store cloudquery files, such as downloaded plugins (default ".cq")
      --invocation-id uuid       useful for when using Open Telemetry integration for tracing and logging to be able to correlate logs and traces through many services (default <NEW-RANDOM-UUID>)
      --log-console              enable console logging
      --log-file-name string     Log filename (default "cloudquery.log")
      --log-file-overwrite       Overwrite log file on each run instead of appending. Use this if your filesystem does not support append mode (e.g. FUSE-mounted cloud storage).
      --log-format string        Logging format (json, text) (default "text")
      --log-level string         Logging level (trace, debug, info, warn, error) (default "info")
      --no-log-file              Disable logging to file
      --telemetry-level string   Telemetry level (none, errors, stats, all) (default "all")
```

### SEE ALSO

* [cloudquery](/cli/cli-reference/cloudquery)	 - CloudQuery CLI


## See Also

- [Schema Migrations](/cli/managing-cloudquery/migrations) - How CloudQuery handles schema changes
- [Destination Integrations](/cli/integrations/destinations) - Configure migration modes
