Import task records, scheduled tasks, memories, and capabilities from Qoder IDE (Quest) and QoderWork into Qoder.
Bring work from other products in the Qoder family into Qoder and continue working there.
Data import is available under Settings › Personal › Data Import. It reads local data from Qoder IDE (Quest) and QoderWork and copies it into Qoder without changing the source. This is a one-time action: it does not set up automatic synchronization or modify or delete any data in the source products.
When you first launch Qoder and sign in, onboarding guides you through Bring your work to Qoder. All importable content is selected by default; you only need to confirm. Return to Settings to import manually in these cases:
The page groups content by source. Within each group, items always appear in this order: task records, scheduled tasks, memories, and capabilities.
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.
Data import is incremental. When new content appears in a source product, select Import Data again to create another batch.
Do you need to import manually?
When you first launch Qoder and sign in, onboarding guides you through Bring your work to Qoder. All importable content is selected by default; you only need to confirm. Return to Settings to import manually in these cases:
- You selected Skip during onboarding.
- You created new task records, scheduled tasks, or memories in the source product after onboarding.
- Source data was unavailable at first launch, and you signed in and used the source product on that computer afterward.
What you can import
The page groups content by source. Within each group, items always appear in this order: task records, scheduled tasks, memories, and capabilities.
| Source | Importable content | Description |
|---|---|---|
| Qoder IDE (Quest) | Task records | Task records from Quest mode, excluding Expert Team tasks |
| Scheduled tasks | Task definitions and historical run records | |
| Memories | Long-term memories, written to the Qoder memory directory | |
| MCP connectors | Skills, subagents, Hooks, and global rules already share the same configuration directory and are inherited automatically; only MCP connectors need to be migrated | |
| QoderWork | Task records | All user conversation records in QoderWork |
| Scheduled tasks | Task definitions and historical run records | |
| Memories | Converted to the standard Qoder memory format | |
| Skills, MCP connectors, and plugins | User-level Skills, MCP connectors, and installed plugins |
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
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 to 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 › Personal › Data Import.
From Settings
1
Check new content
Open Settings › Personal › Data Import. Qoder detects local sources. Each row shows only new content not yet imported successfully, rather than the historical total. A source with no data does not affect other rows.
2
Start importing
Select Import Data to scan again and fix the content for this import. Later records are left for the next import. No empty import starts when there is nothing new.
3
Track progress
The page shows Importing N / 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.
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 N task records found · All imported, 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 | Duplicate filenames are renamed instead of overwriting existing files |
| 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 Separate task output behavior. To keep future runs on one timeline, edit the task and choose Merge task output. 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.
- Memory files: Memories with duplicate filenames are saved under another name and do not overwrite existing content.
- 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.
Troubleshoot import issues
| Message | Meaning and action |
|---|---|
| Unable to read this app's local data. Make sure you have signed in and used it on this computer | 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 Detect Again |
| Unable to detect importable content. Detect again | An error occurred during detection. Select Detect Again to retry |
| No new task records found | The source has no records that have not already been imported. Imported content is not imported again |
| Some content is missing decryption keys and will have reduced display after import | You can import as usual, but some historical content will be incomplete |
| The current host cannot read local source app data. Import from the Qoder desktop app | Data import is available only in the Qoder desktop app |
| Another migration is in progress. Continue after it finishes | Wait for the current batch to finish before starting another import |
Import again
Data import is incremental. When new content appears in a source product, select Import Data again to create another batch.
- Successfully imported task records, scheduled tasks, and memories are not imported again.
- Messages later added to a source task record are not appended to the imported record. Continue that work directly in Qoder.
- After verifying the migration, disable or remove scheduled tasks you no longer use in the source product to prevent duplicate runs.