# Issue with Prodigy 1.11.8a2 with "experimental\_feed"

**URL:** https://support.prodi.gy/t/issue-with-prodigy-1-11-8a2-with-experimental-feed/5708
**Category:** Uncategorized
**Tags:** database
**Created:** [June 15, 2022, 7:27pm UTC](https://support.prodi.gy/t/issue-with-prodigy-1-11-8a2-with-experimental-feed/5708 "2022-06-15T19:27:25Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![magdaaniol](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/magdaaniol/32/2787_2.png) [@magdaaniol](https://support.prodi.gy/u/magdaaniol)
#### Post date: [August 9, 2022, 2:45pm UTC](https://support.prodi.gy/t/issue-with-prodigy-1-11-8a2-with-experimental-feed/5708/4 "2022-08-09T14:45:47Z")

</div>

Hi @nomiizz,  
We have just released`v1.11.8a4`of the alpha that includes the`db-migrate`command ( as well as all improvements that come with the main Prodigy release`v1.11.8`)  
You can download`v1.11.8a4` from our PyPi index like so:

```bash
pip install prodigy==1.11.8a4 --extra-index-url https://{YOUR_LICENSE_KEY}@download.prodi.gy

```

In order to use the`db-migrate`command, you need to specify 1) the legacy DB (v1) and 2) the target DB (v2) in your `prodigy.json`:

```json
{
// prodigy.json
    "experimental_feed": true,
    "feed_overlap": false,
    "legacy_db": "postgresql",
    "legacy_db_settings": {
        "postgresql":{
            "dbname": "prodigy",
            "user": "username",
            "password": "xxx"
        }
    },
    "db": "postgresql",
    "db_settings": {
        "postgresql": {
            "url": "postgresql://username:xxx@localhost:5432/prodigy_v2"
         }
     }
}

```

The legacy DB settings are processed with `peewee` so the configuration style is the same as in v1. The target DB, however, should use`sqlalchemy` style which in the case of `postgresql` is slightly different as explained [here](https://support.prodi.gy/t/duplicate-annotations-in-output/4961/40#overview-1). You can also specify the sqlite or mysql as the target.

With that configuration in place, you should be able to run:

```bash
prodigy db-migrate

```

That should migrate all the datasets from the v1 legacy database to the v2 target database. Also, check  
`prodigy db-migrate --help` for more options (migrating a selected dataset, excluding selected datasets, performing a dry run etc.)

---

_[View the full topic](https://support.prodi.gy/t/issue-with-prodigy-1-11-8a2-with-experimental-feed/5708)._