# Overview Migrating data between two NetSuite accounts is a complex process due to the unique configurations of each account. Unlike transferring data within the same system, NetSuite accounts often differ significantly in terms of their setup, including: * **Chart of Accounts**: Each NetSuite account may have a different structure for managing financial accounts. * **Subsidiaries**: The use of subsidiaries and associated configurations can vary between accounts. * **Custom Fields and Records**: Each account may have custom fields, forms, and workflows that do not exist in the other account. * **Data Structures**: Variances in transaction types, reports, and saved searches can also add complexity. As a result of these differences, there is no direct or automated way to transfer data between two NetSuite accounts. Instead, the data must be treated similarly to a migration from any external system. The process typically involves: 1. **Data Extraction**: Extracting the relevant data (e.g., ledger transactions, customer data, or inventory records) from the source NetSuite account. 2. **Data Transformation**: Aligning the extracted data to match the structure and configuration of the target NetSuite account. This can include mapping accounts, adjusting subsidiary relationships, or modifying custom fields. 3. **Data Loading**: Importing the transformed data into the target NetSuite account using tools like CSV imports, SuiteScript, or APIs. --- # Agent Instructions: 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: ``` GET https://netsuite-data-migration-guide.fowlersconsulting.co.uk/netsuite-to-netsuite-migrations/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.