> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/omnitron/integration/migration/getting-started.md).

# Getting Started

## <mark style="color:red;">General Flow</mark>

* The User, Address, Order, and Order Item information to be migrated is obtained.
* A test User, Address, Order, and Order Item are prepared each.
* Knowledge of the User's password is required.
* Test migration is performed for the User.
* Test migration is performed for Address.
* Test migration is performed for Order.
* Test migration is performed for Order Item.
* Once the tests are successful, the real migration is performed in the same order.

## <mark style="color:red;">Migration Flow Control</mark>

### **Recommended Checklist**

* The User, Address, Order, and Order Item should be migrated in sequence. The progress of each migration\_id received with each request should be monitored. If error\_count:1 is received, before proceeding to the next step, the formats of the data in the sent JSON should be checked.
* After completing the Order Item migration, login should be performed with the credentials of the migrated User.
* On the "My Addresses" page, the arrival of the address should be confirmed at `/account/address/`.
* In the "My Past Orders" page, it should be verified that the migrated order is at `/users/old-orders/`, and the order items are at `/users/old-orders/{pk}`.
* If the testing process is successful, real data should be migrated.

{% hint style="warning" %}
Detailed logs of errors encountered during the migration process are not currently being maintained. Therefore, in the script you'll be writing, we recommend logging each request along with the sent data. This way, in case of any potential errors, you'll be able to debug using the data you've sent.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apidocs.akinon.com/omnitron/integration/migration/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.