> For the complete documentation index, see [llms.txt](https://docs.amigo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amigo.ai/developer-guide/platform-api/data-world-model/bulk-import.md).

# Bulk Import (Migration)

The migration operation imports terminal Classic conversation metadata for existing person entities so migrated history can appear in supported world-model conversation views.

It is admin-only, accepts up to 500 conversations per request, and is idempotent and correctable for a workspace and source conversation ID. It imports conversation metadata rather than transcript turns and does not emit world events for the memory extractor.

## Import Conversation Metadata

{% openapi src="<https://api.platform.amigo.ai/v1/openapi.json>" path="/v1/{workspace\_id}/world/migration/conversations" method="post" %}
<https://api.platform.amigo.ai/v1/openapi.json>
{% endopenapi %}

Use a stable source conversation ID so corrections update the imported record instead of creating duplicates. Timestamps must be timezone-aware, terminal, and internally ordered. Retry only after reconciling the response counts for the prior request.


---

# 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://docs.amigo.ai/developer-guide/platform-api/data-world-model/bulk-import.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.