---
title: "Feature: The \"data-factory:list\" and \"data-factory:import\" commands"
manual: "Data Factory"
version: "2.0"
source: "Changelog/1.0/Feature-DataFactoryCommands.rst"
rendered: "2026-09-27T15:20:47+00:00"
---

# Feature: The "data-factory:list" and "data-factory:import" commands {#feature-data-factory-commands}

## Description {#description}

Two console commands make the seed sets of an installation visible and import
one of them.

```bash
vendor/bin/typo3 data-factory:list
vendor/bin/typo3 data-factory:import demo --dry-run
vendor/bin/typo3 data-factory:import demo --base='https://example.com/'
```

`data-factory:list` prints identifier, title and providing extension of every
seed set found in `Configuration/DataFactory/*/config.yml` of an active
extension, in the order the installation loads its extensions in. `-v`
adds the directory of each set. An identifier provided by more than one
extension is reported with all of its providers and makes the command exit
non-zero: the sets cannot be told apart, so neither listing nor importing may
pick one of them.

`data-factory:import` writes one set. Without an identifier it asks which one;
without a terminal to ask on it lists the available sets and exits non-zero
rather than guessing. The options are:

| Option | Effect |
| --- | --- |
| `--dry-run` | Validate the set and report what an import would do, writing nothing. |
| `--force` | Import although the set suggests uids this installation already uses. |
| `--root-page` | The page the set is written below. `0` is the page tree root. |
| `--base` | Replaces the `base` of every site configuration the set writes. |
| `--no-site-config` | Skip the site configurations the set declares. |

Each kind of failure has its own exit code — unknown set, unresolvable set,
invalid definition, uid collision, no administrator, failed write — so that a
deployment script can tell "no such set" from "that would overwrite something"
without parsing the output. The complete list is in the
[Configuration](../../Configuration/Index.html#configuration-command-import) chapter.

## Impact {#impact}

An installation can be provisioned from the command line, and a pipeline can act
on what happened. The complete option and exit code reference is in the
[Configuration](../../Configuration/Index.html#configuration) chapter.