Move Your Project Between Tools and Export It
Updated · Tech checked
Exported files plus a written handoff carry the project anywhere; a new tool reads files, not your old chat.
The direct answer
Portability is files plus a handoff note. Export the three files, write the 20-line handoff (goal, decisions, open bugs, next task), and the next tool starts from files, never from your old conversation.
Step by step
- Export all files with their names intact.
- Write the handoff: goal, decisions, open bugs, next task; no secrets, no full history.
- In the new tool, introduce the files first and ask for a one-line summary each.
- Run your five checks in the new place before changing anything.
- Change one thing and re-run the checks.
Worked example
Tracker moves from builder to editor: same files, handoff names the filter decision and the open save bug, next task is export. Lab A18 builds exactly this package.
Errors to avoid
- Pasting chat history as context. Twenty lines beat two hundred.
- Including secrets in the handoff. Synthetic examples only.
- Changing code before the checks pass in the new tool.
Frequently asked questions
Can I switch tools mid-course? Yes. The course is tool-independent; files and handoffs are the contract.
Who owns the exported code? You do, under the tool's terms for generated output; check the terms of the tool you use (checked 2026-10-04).
Sources
- Course lessons M06 and lab A18 (this site).
- Tool output terms: official terms pages (checked 2026-10-04).