Skip to main content

Import data

Bring work from IDE, QoderWork, WorkBuddy, Codex, Kiro IDE, 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.

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, confirm that the source app was used while signed in on this computer. Qoder IDE uses the source for the same region as the current client. QoderWork and QoderWork CN appear as separate sources when their local data is detected; choose the one you need. For other sources, follow the detected items and supported import scope shown on the page.
SourceImportable contentBefore importing
Local Qoder IDE (Quest)Task records, schedules and run history, memories, MCPSkills, subagents, Hooks, and global rules already share a configuration directory and are inherited.
Local QoderWorkTask records, schedules and run history, memories, user-level Skills, MCP, and pluginsMemories are converted to the Qoder format. Project-level and local-level plugins are excluded.
Local WorkBuddyTask records, schedules, memories, Skills, MCP, and pluginsChanged memories overwrite their corresponding targets. Save a copy first if you need to keep manual edits to those files.
Local CodexTask records, supported scheduled tasks and run records, memory, and compatible Skills, MCP, and pluginsSelect from the detected items. Newly imported scheduled tasks do not run automatically.
Local Kiro IDETasks, memory, and supported user-owned Skills, MCP configurations, and PowersSelect detected items; this does not import all app settings, scheduled tasks, or previous automatic-approval permissions.
Qoder IDE(Quest) over Remote SSHTask records, memories, MCPConnect 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. Find Qoder IDE, QoderWork, WorkBuddy, Codex, or Kiro IDE, select Check again, then expand a source and choose 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. Missing data or an unreadable source is explained without affecting other sources.
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 Codex

  1. Open Settings → Data import → Import from apps, run detection again, and expand Codex to review the counts for each category.
  2. Clear categories you do not need. Selection is by task records, scheduled tasks, memory, or Skills, MCP connectors, and plugins, rather than by individual record. To migrate only automations, select only scheduled tasks.
  3. Use the Codex import button and keep the app running until the import finishes. Review successful, skipped, and failed items.
  4. For scheduled tasks, open Automation in the sidebar. Use a task’s menu to edit and review its prompt, schedule, time zone, model, and execution environment. Use the same menu to view imported run history.
Newly imported scheduled tasks remain disabled and do not run automatically. Enable them only after reviewing their configuration for use in Qoder. Only supported local automations and compatible extensions migrate. Codex-specific runtimes, application-specific plugins, and computer-use MCP connections are excluded. Imported plugins start disabled; attachments, capability selections, and original approval modes are not guaranteed to carry over. Unreadable, oversized, conflicting, or incompatible Codex records may be skipped. Follow the result details for each item, and check dependencies and permissions before enabling imported plugins. Codex task imports retain multi-directory workspace information. After opening an imported task, check that its linked directories are accessible; import does not copy the project files.

Import from Kiro IDE

Open Settings → Data import → Import from apps, detect again, and expand Kiro IDE. Review the available categories and select the content you need. Check successful, skipped, and failed items afterward, and reauthorize connectors when prompted. Detect and import again for new tasks or supported updates; tasks continued in Qoder are not directly overwritten by the source. Import copies the selected content without establishing continuous synchronization.

Import from Remote SSH

Remote import supports Qoder IDE task records, memories, and MCP.
  1. Add and connect an SSH host under Settings → Connections.
  2. Return to Data import → Import from SSH instances and select Check again.
  3. Expand the instance, select categories, and use its import button.
  4. Check each result. Resolve disconnected hosts, missing sources, or partial failures before detecting again.
For help connecting the host, see SSH workspaces.

Import again

For Qoder IDE, QoderWork, WorkBuddy, Kiro IDE, and Remote SSH, check for updates to imported tasks as described below. For Codex, use the results of a new detection scan. 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. For sources that support importing again, an unreadable image is skipped while other readable content continues to import. Check important attachments afterward; this does not guarantee recovery of every historical image.

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.
ContentHow to confirm completionWhat to note
Task recordsThe page shows Imported all N task records., and the records open from the sidebarOne failed record does not stop the batch
Scheduled tasksThe page confirms that tasks and run history were importedNewly imported tasks do not run automatically
MemoriesThe page shows the number importedIDE / QoderWork duplicates are renamed; WorkBuddy may overwrite its corresponding targets
Skills, MCP, and pluginsThe page shows migrated, skipped, unsupported, and reauthorization countsOAuth connectors require authorization again
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.

Make imported content ready to use

Scheduled tasks

All imported scheduled tasks are disabled by default to prevent the same task from running in two products. Review the schedule and task content before enabling each task manually.
  • 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

MessageMeaning 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
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.