> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/v1/move/explore-moved-data.md).

# Explore moved data

A pipeline reporting `active` means it is running, not that the data is right. Before you productize, confirm the data actually landed and looks the way you expect. This is the same inspection you did in [Understand](/build/v1/understand/explore-data.md), now pointed at the destination.

## Verify the move

Check three things, in order.

**1. The pipeline ran.** Confirm the resource is healthy and look at its run history:

```bash
dataos-ctl resource get -t nilus -n ${{pipeline-name}}
```

**2. The tables are discoverable.** Open [Datasets](/build/v1/understand/explore-data/datasets.md) and find the destination tables. Confirm the schema, columns, and types match the source, and that the row counts are in the range you expect.

**3. The values are correct.** Open the destination in [Workbench](/build/v1/understand/explore-data/workbench.md) and sample the data. Check that:

* Row counts match the source, or match the increment for a scheduled or change-based run.
* Key columns are populated and unique where they should be.
* Dates, numbers, and categories landed in the right types, not as strings.
* For CDC, updates and deletes are reflected the way your sink strategy intends (`append` keeps history; `merge` reflects current state).

## When the data does not look right

| Symptom                    | Where to look                                                                                                                                                         |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tables missing in Datasets | The pipeline failed or the sink Depot is wrong. Re-check the manifest and run history.                                                                                |
| Fewer rows than expected   | Scope filters, an incremental key that excludes rows, or a first run still in progress.                                                                               |
| Wrong types or shapes      | [Schema evolution](https://v2.dataos.info/references/resources/nilus/concepts/schema-evolution) behavior, or a source change the pipeline has not picked up.          |
| Sensitive fields visible   | Add [data masking](https://v2.dataos.info/references/resources/nilus/concepts/understanding-data-masking) to the move. Masking is a handling policy, not a transform. |

## Next

The data is in reach and verified. Move on to [Productize](/build/v1/productize/overview.md) to turn it into a Data Product.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/build/v1/move/explore-moved-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.