> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/survey-programming-decipher/legacy-to-unified-transition.md).

# Legacy to Unified Transition

Switching from the Legacy Metaforms Decipher Workflow to the new Unified Workflow introduces a number of changes that streamline your research and survey programming process. This tutorial highlights what's different, guides you through the updated steps, and points out the advantages of the Unified Workflow.

## Introduction

In the Unified Workflow, you'll notice new navigation paths, a reorganized interface, and smarter automation, especially with the integration of AI-driven features. While much of the process remains familiar, the location of key actions and some functionalities have shifted to enhance productivity and reduce manual effort.

This guide outlines the key nuances for users transitioning from the Legacy Decipher Flow to the Unified Flow, helping you understand what's changed and how to make the most of the new experience.

Use the sections in this guide to follow the flow in order, or jump to a topic from the table of contents.


---

# 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://help.metaforms.ai/survey-programming-decipher/legacy-to-unified-transition.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.
