From 83041d8bc4f7ccabe0e24b86d735a7893ffa96dc Mon Sep 17 00:00:00 2001 From: pierwill Date: Wed, 26 Aug 2020 14:45:51 -0700 Subject: [PATCH] Address PR feedback --- content/v2.0/write-data/bulk-ingest-cloud.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/v2.0/write-data/bulk-ingest-cloud.md b/content/v2.0/write-data/bulk-ingest-cloud.md index c484af911..9c24a68f1 100644 --- a/content/v2.0/write-data/bulk-ingest-cloud.md +++ b/content/v2.0/write-data/bulk-ingest-cloud.md @@ -12,9 +12,9 @@ menu: products: [cloud] --- -The InfluxDB API is the way to feed ongoing collection of data into InfluxDB. -However, you might want to upload a large amount of previously existing *historical* data into InluxDB Cloud. +You might want to upload a large amount of previously existing *historical* data into InluxDB Cloud. Given our usage-based pricing and the fact that the API is optimized for batched writing, the API is not recommended in the case of bulk data. -Users who need to ingest bulk data chould contact support to review the limits, volume, and coordinate their efforts. -This may include running a small sample of the data into a test bucket so that a schema review can also be performed. +To migrate a large amount of existing historical data to Cloud, contact Support for assistance. +We’ll review your ingest rate limits, volume, and existing [data schema](/v2.0/reference/key-concepts/data-schema) to ensure the most efficient migration. +