---
title: "Amplia Reg command: **migrate-data**"
description: "Amplia Reg command migrate-data: schedules a background job that migrates application data to a new schema version, with a batch size option."
canonical: "https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/tool/migrate-data"
locale: "en"
product: "Amplia Reg"
last_updated: "2026-07-14"
---

# Amplia Reg command: **migrate-data**

## Name

`migrate-data` - Migrates application data to match a new schema version

## Syntax

```sh
dotnet Lacuna.AmpliaRegNg.Site.dll [settings] -- migrate-data --to <to-version>
```

Or, on Docker:

```sh
docker run -i lacunasoftware/ampliareg:x.y.z [settings] -- migrate-data --to <to-version>
```

> **Info**
>
> Replace `x.y.z` above with the version indicated on the update procedure

The `settings` arguments are additional settings to overwrite settings from configuration files and environment variables,
for instance `--Section1:Name1=value1 --Section2:Name2=value2`.

Options:

* `--batchsize <batch-size>`: Number of records to update per iteration. Default: 100

## Description

The `migrate-data` command schedules a background job to update data to conform to the given target schema version.

After running the command, follow the steps below to monitor the update job:

1. Sign-in to your Amplia Reg instance
1. Click on your name on the top right corner, then on **Hangfire**
1. Click on **Jobs** on the top menu
1. Look for the job named `IDataMigrationJob.RunAsync` on the **Processing** job list
1. Wait until the job transitions to the **Succeeded** job list
1. Check the application logs to see if any error occurred

## See also

* [Amplia Reg command-line tool](https://docs.lacunasoftware.com/en-us/articles/amplia-reg/on-premises/tool)