# Ingesting old data to a TSDS - Problems?

**URL:** <https://discuss.elastic.co/t/ingesting-old-data-to-a-tsds-problems/369174>\
**Category:** Elasticsearch\
**Tags:** datastreams\
**Created:** [October 21, 2024, 5:53pm UTC](https://discuss.elastic.co/t/ingesting-old-data-to-a-tsds-problems/369174 "2024-10-21T17:53:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![deedubbs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deedubbs/32/134913_2.png) [@deedubbs](https://discuss.elastic.co/u/deedubbs)\
**Post date:** [October 21, 2024, 5:53pm UTC](https://discuss.elastic.co/t/ingesting-old-data-to-a-tsds-problems/369174/1 "2024-10-21T17:53:45Z")

</div>

We are about to stand up a time series datastream for some metrics data that we've been tracking via multiple indices. One of the notes on the TSDS documentation page suggests that you should only use a TSDS "if you typically add metrics data to Elasticsearch in near real-time and `@timestamp` order.

That will be the case moving forward. However, we have some historical data that we want to include. It needs to be re-ingested (via a script (of that matters), not a reindex, since the data structure needs to be changed). This is on the order of 10 million documents. Is this going to cause an issue?