[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-25 (世界標準時間)。"],[],[],null,["# Admin settings - Export\n\n| **Note:** Exports can only be imported into a Looker (Google Cloud core) instance. Exports cannot be imported into a Looker (original) instance.\n\nYou will see the **Export** page in your instance if all of the following situations are true:\n\n- You are using a Looker (original) instance and not a Looker (Google Cloud core) instance.\n- Your Looker (original) instance is Looker-hosted and not customer-hosted.\n- You have the [Admin role](/looker/docs/admin-panel-users-roles#permission_sets) in the Looker instance.\n\nYou use the **Export** page when you are performing [self-service migration](/looker/docs/looker-core-self-service-migration).\n\nThe **Export** page is where you perform these tasks:\n\n- Create a request to export the data from your existing Looker (original) instance so that it can be migrated to the [Looker (Google Cloud core) environment](/looker/docs/looker-core-overview).\n- View the status of any submitted requests.\n\nSee the [Self-service migration from Looker (original) to Looker (Google Cloud core)](/looker/docs/looker-core-self-service-migration) documentation page for information about how to generate the information that needs to be entered onto the **Export** page and how to complete the migration.\n| **Important:** Before you can undertake a migration, you must have already upgraded your existing Looker (original) contract to cover Looker (Google Cloud core) and validated with your account representative that you are eligible for migration. When you sign the Order Form to purchase Looker (Google Cloud core), your Looker (original) license will be set to expire 60 days from the signing date.\n\nEntering export information\n---------------------------\n\nFollow the steps on the [Self-service migration from Looker (original) to Looker (Google Cloud core)](/looker/docs/looker-core-self-service-migration) documentation page up to the [Request the export](/looker/docs/looker-core-self-service-migration#request-export) section. Then enter the following information into the **Export** page in your Looker (original) instance:\n\n- The name of the Cloud Storage bucket that you created\n- The Cloud Storage folder name\n- The [name of the KMS key](/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version) used to encrypt the migration data\n- The JSON text that contains the service-account key\n\n| **Important:** Don't share the JSON key file outside of the **Export** page. If you need support, Cloud Customer Care will advise you on how to share the file---don't send it in an email or write it in cleartext in a Support ticket.\n\nOnce you have entered the information, click **Request Export** to initiate the export.\n\nWhen you click the **Request Export** button, it triggers a background process that exports the data to the specified Cloud Storage bucket. This can take a few hours.\n\nThe export operation shouldn't cause any disruption or require downtime in your Looker (original) instance.\n\nList of export requests\n-----------------------\n\nOnce an export request has been submitted, it will appear in a table at the bottom of the **Export** page, with one of the following statuses:\n\n- **REQUESTED** --- Export request has been submitted but export has not begun.\n- **PROCESSING** --- Export operation has begun but is not completed.\n- **COMPLETE** --- Export operation is complete and data files should be in the Cloud Storage bucket that is listed in the request.\n- **ERROR** --- Export operation was not complete due to an error. Clicking the **ERROR** status reveals an error message.\n\nThe export process takes a few hours. Return to the **Export** page to view the status of the request during that time.\n\nOnce the export has been completed and the data appears in your Cloud Storage bucket, continue with the steps on the [Self-service migration from Looker (original) to Looker (Google Cloud core)](/looker/docs/looker-core-self-service-migration) documentation page, beginning with the [Import the data into the new \"empty\" Looker (Google Cloud core) instance](/looker/docs/looker-core-self-service-migration#import-data) section, to complete the migration.\n| **Important:** Any changes that you make in the Looker (original) instance after export won't be carried over to the Looker (Google Cloud core) instance. If you need to migrate fresh data to your Looker (Google Cloud core) instance, you can request additional export operations and migrate new instance data into Looker (Google Cloud core). However, importing fresh data into your Looker (Google Cloud core) instance will overwrite any customizations that have been made to that instance.\n\nIssues during export\n--------------------\n\nIf an issue occurs with the export of your Looker (original) data, a status of **ERROR** will appear in the row of the export request. Clicking the **ERROR** status reveals an error message.\n\nCommon sources of errors are the following:\n\n- The Cloud Storage bucket, KMS key, or `\u003cexport-service-account\u003e` is invalid.\n- The `\u003cexport-service-account\u003e` lacks the necessary permissions.\n\nIt is helpful to confirm the status of these objects before submitting your export request."]]
