> 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/esim-transfer-re-issuance.md).

# eSIM Transfer / Re-issuance

If an eSIM has been activated on the wrong device, or needs to be moved to a different device, you can request a re-issuance directly through the Partner Portal.

**What it is**

Re-issuing an eSIM deactivates the current eSIM and issues a replacement with a new QR code. This is used specifically when an eSIM needs to be set up on a different device than originally activated.

**How to do it**

1. Login to the Partner Portal: <https://partners.hostednetwork.com.au/>
2. Navigate to the relevant Telstra Mobile service.
3. Click the **Action** button at the top of the page, then select **Manage eSIM**.
4. Select **Reissue eSIM**.
5. Enter the email address the new QR code should be sent to.
6. Click the button to proceed, the request will process automatically.

**Important to know**

* This deactivates the current eSIM immediately.
* A **once-off eSIM reissue fee** applies.

**Need help?**

If you're unable to complete this yourself, please reach out to our Support Team, who can process this on your behalf.


---

# 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/esim-transfer-re-issuance.md?ask=<question>&goal=<user_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.