> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/legacy-tools-and-migration.md).

# Legacy Tools and Migration

Use this page when an existing workflow contains an older tool. Deprecated tools are not recommended for new work. Some older actions no longer perform an operation; others require replacing their inputs and output mappings with a current tool.

## Choose a replacement

| Older tool                                                                                        | Current approach                                                                                                                                                                          |
| ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Search Knowledge Bases](/stackai-tools/knowledge-base-access/search-knowledge-bases.md)          | [Search Knowledge Base](/stackai-tools/knowledge-base-access/search-knowledge-base.md). Select the intended base and review search settings and result mappings.                          |
| [Explore Folders](/stackai-tools/knowledge-base-access/explore-folders.md)                        | [List Knowledge Base Contents](/stackai-tools/knowledge-base-access/list-knowledge-base-contents.md). Check folder identifiers and returned file fields.                                  |
| [Read File](/stackai-tools/knowledge-base-access/read-file.md)                                    | [Read Knowledge Base File](/stackai-tools/knowledge-base-access/read-knowledge-base-file.md). Map the selected base and file explicitly.                                                  |
| [Terminal (Legacy StackAI)](/stackai-tools/legacy-tools-and-migration/terminal-legacy-stackai.md) | [Terminal (StackAI Computer)](/stackai-tools/browser-and-computer/terminal-stackai-computer.md) when available. Review commands, paths, and returned fields.                              |
| [File Navigation](/stackai-tools/legacy-tools-and-migration/file-navigation.md)                   | Choose a current file or Computer tool for the operation. There is no automatic one-to-one replacement.                                                                                   |
| [Task Scheduler](/stackai-tools/time-and-scheduling/task-scheduler.md)                            | [Scheduled Execution](/stackai-tools/built-in-triggers/scheduled-execution.md) starts a workflow on a schedule. Rebuild the task as a workflow; this is not a drop-in action replacement. |
| [Rename Conversation](/stackai-tools/legacy-tools-and-migration/rename-conversation.md)           | [Update Conversation Title](/stackai-tools/communication-and-human-input/update-conversation-title.md) for a supported chat session.                                                      |

## Remove obsolete chat actions

[Send Simple Message](/stackai-tools/legacy-tools-and-migration/send-simple-message.md), [Send Loading Message](/stackai-tools/legacy-tools-and-migration/send-loading-message.md), [Send Tool Render Message](/stackai-tools/legacy-tools-and-migration/send-tool-render-message.md), [Send Message with Buttons](/stackai-tools/legacy-tools-and-migration/send-message-with-buttons.md), and [Rename Conversation](/stackai-tools/legacy-tools-and-migration/rename-conversation.md) are deprecated and no longer perform their named operations. Remove dependencies on their behavior.

Use the workflow's normal output for a final response. Use [Ask Human in Chat Interface](/stackai-tools/communication-and-human-input/ask-human-in-chat-interface.md) when an agent needs a reply from the user, and [Generate UI](/stackai-tools/content-and-interface-generation/generate-ui.md) when a supported chat interface needs structured content. These serve different purposes; they do not reproduce every old message or button behavior automatically.

## Deployment-specific file creation

[Canvas Write File](/stackai-tools/legacy-tools-and-migration/canvas-write-file.md) is a fallback available in some deployments without StackAI Computer. It is not universally deprecated. Where Computer is available, create files with [Terminal (StackAI Computer)](/stackai-tools/browser-and-computer/terminal-stackai-computer.md) and share an existing file with [Canvas Share File](/stackai-tools/browser-and-computer/canvas-share-file.md).

## Check a migration before publishing

1. Identify which later steps use the old tool's results and which behavior the user depends on.
2. Add the replacement in the working draft. Map required inputs and inspect its actual returned fields.
3. Update downstream mappings. Check files, permissions, chat behavior, and error handling as applicable.
4. Run representative requests and compare the results with the intended task. Follow your normal release process after verifying the revised workflow.

Do not remove a working dependency merely because a similarly named tool exists. If the required replacement is unavailable, ask your organization administrator or StackAI support about availability before changing a published workflow.


---

# 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.stackai.com/stackai-tools/legacy-tools-and-migration.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.