> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/connectivity/lte-services/telstra-mobile-data/transferring-a-service-between-data-pools.md). # Transferring a Service Between Data Pools #### Understanding Data Pools A **data pool** allows a group of SIMs to share a combined data allowance, rather than each SIM having its own separate limit. This is useful when some services use very little data and others use a lot, since the unused allowance from lighter users is available to the rest of the pool. Each pool supports up to **300 SIMs**, and every SIM in a pool must be on a **Pooled** plan (data pooling isn't available on Banked plans). Pools come in two types, set when the pool is created: * **Auto Top-up** — if the pool's total data is exceeded, an additional 10GB block is automatically added. * **Non Auto Top-up** — if the pool's total data is exceeded, the pool does not automatically top up. Individual services may still incur excess usage charges unless their excess spend limit is set to $0. A pool can only be **one type or the other**, it can't be changed after creation. If you need the other type, a new pool needs to be created. #### Billing Cycle & Pool Allowance * The billing cycle runs from the **28th to the 27th of each month**, and pool allowances reset at the start of each new cycle. * Unused data does **not** roll over between cycles, data pooling doesn't include a banking/rollover feature (that's only available on standalone Banked plans). * Usage alerts are triggered at 50%, 80%, and 100% of the pool's total allowance. #### Transferring a Service Between Pools Services **can** be transferred from one pool to another, for example, if a customer's usage pattern has changed, or you're consolidating services across pools. **This isn't currently available as a self-service option in the Partner Portal.** To transfer a service between pools, please raise a support ticket with the following details: * The service ID (or mobile number) of the SIM to be transferred * The current pool it's in * The pool you'd like it moved to (or let us know if a new pool needs to be created first) * When the service will be moved (Immediately, or next billing cycle) Our Support team will action the transfer for you. **Please note:** transferring a service between pools immediately does not carry over any data usage history or contribution, the service simply starts drawing from the new pool's allowance going forward. #### What's Coming Self-service pool transfers are on our development roadmap, so this can eventually be managed directly in the Partner Portal without needing to raise a ticket. We'll update this article once that capability becomes available. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kb.hostednetwork.com.au/support/services/connectivity/lte-services/telstra-mobile-data/transferring-a-service-between-data-pools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.