Bring work from IDE, QoderWork, WorkBuddy, or a remote SSH host into Qoder.
Import existing task records, memories, and extension settings into Qoder to continue your work. Open Settings → Data import and choose a local app or a connected SSH instance. Each import copies the selected content without changing its source or setting up continuous synchronization.
Choose a source based on where your data is stored. Qoder lists the detected categories and available items for that source.
For local sources, import reads data on this computer. Local sources must have been installed and used while signed in on the same computer. Qoder-family source products must be in the same region as your current Qoder installation: Qoder reads Qoder data, while Qoder CN reads Qoder CN data. Data is not transferred across regions.
On first sign-in, onboarding lets you review and import detected local content. If you skip onboarding, use a source app later, or create new content there, return to Settings to detect and import it. For remote data, use Import from SSH instances on the same page.
Remote import supports Qoder IDE task records, memories, and MCP.
Detecting a source again can find eligible updates to previously imported tasks as well as new tasks. Select Check again under Settings → Data import, review the available categories and counts, then select the import button for that source. Task records from local apps and Remote SSH are processed according to the detection results.
Source updates do not directly overwrite records you have continued or modified in Qoder. If a task is running or occupied by another operation, wait or follow the displayed guidance. Records without an eligible update are not duplicated. This flow does not merge conversations independently continued in both products or set up continuous synchronization.
Previously imported schedules are not duplicated. Changed WorkBuddy memories still overwrite their corresponding target files; task-record protections do not apply to memory files. Save a separate copy of manual edits you want to keep.
After verifying the migration, disable or remove scheduled tasks you no longer use in the source product to prevent duplicate runs.
When the import finishes, return to Data import to review the imported, skipped, and failed counts. Use the checks below to confirm your content is ready to use. Import started means the import is still in progress.
If an item fails, the page reports the imported and failed counts with a reason, such as a missing file. One failed record does not stop the rest of the import.
Skipped Skills are listed separately in the import results with their names and source directories. Source files are not modified. Check these directories before trying the migration again.
What you can import
Choose a source based on where your data is stored. Qoder lists the detected categories and available items for that source.
For local sources, import reads data on this computer. Local sources must have been installed and used while signed in on the same computer. Qoder-family source products must be in the same region as your current Qoder installation: Qoder reads Qoder data, while Qoder CN reads Qoder CN data. Data is not transferred across regions.
| Source | Importable content | Before importing |
|---|---|---|
| Local Qoder IDE (Quest) | Task records, schedules and run history, memories, MCP | Skills, subagents, Hooks, and global rules already share a configuration directory and are inherited. |
| Local QoderWork | Task records, schedules and run history, memories, user-level Skills, MCP, and plugins | Memories are converted to the Qoder format. Project-level and local-level plugins are excluded. |
| Local WorkBuddy | Task records, schedules, memories, Skills, MCP, and plugins | Changed memories overwrite their corresponding targets. Save a copy first if you need to keep manual edits to those files. |
| Qoder IDE（Quest） over Remote SSH | Task records, memories, MCP | Connect the host first. Remote schedules and plugins are not imported. |
What is not imported
- Credentials: Configure model API keys, OAuth authorizations, and SSH credentials again in Qoder.
- Project files: Import preserves task records and references to their working directories; it does not copy project files.
- Plugins outside user scope: QoderWork project-level and local-level plugins are supplied by the enterprise or workspace. Only user-level plugins are migrated.
QoderWork is available only for macOS and Windows. The QoderWork group does not appear on Linux.
Import your data
On first sign-in, onboarding lets you review and import detected local content. If you skip onboarding, use a source app later, or create new content there, return to Settings to detect and import it. For remote data, use Import from SSH instances on the same page.
Keep Qoder running during import, especially while importing memories and capabilities. Task records can import in the background. If you quit the app or it is forcibly closed, reopen it and select Continue import. You do not need to close the source Qoder IDE or QoderWork app; their data is read only.
During first launch
1
Review the content
After signing in to Qoder, check the sources and content on the Bring Your Work into Qoder page. All importable items are selected by default. To exclude an item, expand its source and clear the checkbox.The onboarding page groups items by source, including Conversation data, Scheduled tasks, MCP connectors, and Memory.
2
Start the import
Select Continue. Data imports in the background, and closing the onboarding window does not interrupt it.
3
Check the result
Completion notifications appear in the main window. Task records and their original working directories appear in the sidebar; a large import may take some time.
Selecting Skip during onboarding does not remove any data. You can run the same flow later from Settings → Data import → Import from apps.
From Settings
1
Review available imports
Open Settings → Data import → Import from apps. Select Qoder IDE, QoderWork, or WorkBuddy under Import from apps, then select Check again and choose the categories to import. Each row shows content available from this scan, not the historical total; task records may include new tasks and eligible source updates. A source with no data does not affect other rows.
2
Start importing
Select the import button for that source. Check the categories and count; the button is unavailable when no content can be imported. Later records are left for the next import.
3
Track progress
The page shows Importing N of M.... Task records are processed one at a time in the background, so large imports may take longer. Leaving and returning preserves progress and does not start another import.
4
Pause or cancel when needed
Select Pause import to stop after the current item finishes, or Cancel import to stop processing the remaining content. Both actions preserve content already imported.
5
Continue after an interruption
If you quit Qoder or the app is forcibly closed, reopen it and select Continue import. Only the remaining content originally selected is processed.After reopening, the page shows the unfinished import with imported and remaining counts. Continuing does not select everything again or create duplicates. Content added to the source during a pause is left for the next import.
Only one import can run at a time, including across sources. Wait for the current import to finish before starting another.
Import from Remote SSH
Remote import supports Qoder IDE task records, memories, and MCP.
- Add and connect an SSH host under Settings → Connections.
- Return to Data import → Import from SSH instances and select Check again.
- Expand the instance, select categories, and use its import button.
- Check each result. Resolve disconnected hosts, missing sources, or partial failures before detecting again.
Import again
Detecting a source again can find eligible updates to previously imported tasks as well as new tasks. Select Check again under Settings → Data import, review the available categories and counts, then select the import button for that source. Task records from local apps and Remote SSH are processed according to the detection results.
Source updates do not directly overwrite records you have continued or modified in Qoder. If a task is running or occupied by another operation, wait or follow the displayed guidance. Records without an eligible update are not duplicated. This flow does not merge conversations independently continued in both products or set up continuous synchronization.
Previously imported schedules are not duplicated. Changed WorkBuddy memories still overwrite their corresponding target files; task-record protections do not apply to memory files. Save a separate copy of manual edits you want to keep.
After verifying the migration, disable or remove scheduled tasks you no longer use in the source product to prevent duplicate runs.
Verify the result
When the import finishes, return to Data import to review the imported, skipped, and failed counts. Use the checks below to confirm your content is ready to use. Import started means the import is still in progress.
| Content | How to confirm completion | What to note |
|---|---|---|
| Task records | The page shows Imported all N task records., and the records open from the sidebar | One failed record does not stop the batch |
| Scheduled tasks | The page confirms that tasks and run history were imported | Newly imported tasks do not run automatically |
| Memories | The page shows the number imported | IDE / QoderWork duplicates are renamed; WorkBuddy may overwrite its corresponding targets |
| Skills, MCP, and plugins | The page shows migrated, skipped, unsupported, and reauthorization counts | OAuth connectors require authorization again |
Make imported content ready to use
Scheduled tasks
- Task output: Scheduled tasks retain the source product's Independent task behavior. To keep future runs on one timeline, edit the task and choose Merged task. The change applies from the next run; imported historical runs remain separate.
- Working directory: A virtual or missing local directory is not retained. Select a working directory again in the task editor.
- Task limit: Qoder stores up to 50 scheduled tasks. If existing tasks plus tasks to import exceed 50, the excess tasks are skipped and included in the result count.
Connectors, plugins, and memories
- Connector authorization: Follow the import results to authorize OAuth connectors again before using them.
- Duplicate capabilities: If an MCP connector or plugin with the same name already exists, the imported item is skipped without comparing content or versions, overwriting it, or renaming it. A connector disabled in QoderWork remains disabled. The local enabled setting is preserved.
- Historical content: If a source record is missing its content decryption key, the task record can still be imported, but some content appears in a reduced form. Qoder warns you before import.
- IDE / QoderWork memories: Duplicate filenames are saved under another name without overwriting existing memories.
- WorkBuddy memories: Missing targets are created, identical content is skipped, and changed content overwrites the corresponding target file. Save a separate copy of any manual edits you want to keep before importing again.
Troubleshoot import issues
| Message | Meaning and action |
|---|---|
| Qoder cannot read this app's local data. Make sure you have used it on this device. | The source product has not been used while signed in on this computer, or its data directory is currently unreadable. Sign in to the source product, then select Check again |
| Qoder could not check what can be imported. Check again. | An error occurred during detection. Select Check again to retry |
| No new task records were found. | This scan found no new tasks or eligible updates. Select Check again after source content changes; records continued or modified in Qoder may be excluded from updates |
| Some message bodies have no decryption key and will be imported in a degraded form. | You can import as usual, but some historical content will be incomplete |
| This host cannot read local source app data. Import from the Qoder desktop app. | Data import is available only in the Qoder desktop app |
| Another source is importing. You can start once it finishes. | Wait for the current batch to finish before starting another import |