> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/platform-guides/google/performance-and-limits.md). # Performance and Limits Like most cloud storage providers, Google Drive has limitations that impact migration performance. ### Team drives are limited to 500,000 objects Google limits Team drives to a maximum of 500,000 objects. Once you reach this limit, you are unable to add new objects to the team drive. ### Folder nesting limit A folder in a Shared Drive in Google Workspace can have up to 100 levels of nested folders. If a folder in the source has more than 100 subfolders, the data folder architecture will need to be restructured to fit in Google Workspace. ### Google docs export limit Google does not allow Documents/Sheets/Presentations greater than 11MB in size to be exported into standard Microsoft formats via their API. Files exceeding this limit must be manually exported directly from the Google web frontend. ### Daily upload limit per user For individual users, Google has a daily upload limit of 750GB per user. Once this limit is hit, rate limiting prevents new objects from being uploaded ### Daily download limit per user Depending on the tenant, there is an undisclosed download limit. We believe this limit is around 13TB per day, but it varies between tenants. ### Rate limiting Google rate limits API queries. This creates an ultimate bottleneck during migrations that we cannot surpass. Movebot has very high quota limits, so generally rate limiting does not impact the performance much beyond what is described above. \ Tags: googledrive --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.movebot.io/platform-guides/google/performance-and-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.