> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/surveys/question-configuration/replace-question.md).

# Replacing a Survey Question in an existing Survey

After a question has been created, you are not able to change the Question Type.

After a question has been created, you are not able to change the **Question Type**. This is to prevent data loss in case someone has answered the survey already. If you want to change the **Question Type** of an existing question, you need to delete the original question and then create a new question with the new **Question Type** in its place.

***Note:** Before deleting the existing question, note any attributes it has that you might need to carry forward to your new question (e.g. Settings, Respondent Attribute, Answer Options and Settings). The most important field to take note of is the **Question #**. You need the **Question #** of the **existing** survey question to enter in the **Question #** field of the new replacement question you are creating.*

* Identify the Question you want to replace and click on the Edit pencil icon (<i class="fa-pencil">:pencil:</i>);
* Make note of the Question # (and any other attributes you want to reuse in the new question);
* Create your new question, by clicking on the Add Question button at the top of the page, and add the existing Question # in the new questions Question # field;
* Add the content for your new Survey Question and click the Save button.
* Delete the existing Survey Question you wanted to replace.

**Important Note: Deleting an existing question (or survey answer option) in a Survey will delete any responses associated with that question. Once a survey is active, and a question or answer option needs to be updated/replaced/removed, it is better to create a new Survey.**


---

# 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://docs.shiftiq.com/help/surveys/question-configuration/replace-question.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.