InteractiveOpen

Scientific computing

Move from Jupyter

Bring the scientific project intact while being explicit about notebook UI versus script/runtime workflows.

Typical migration: Moderate · Best method: Local folder · Git · ZIP

Before You Move

  • Collect `.ipynb`, scripts, datasets and environment/requirements files.
  • Record kernel/package versions when reproducibility matters.
  • Identify generated files that should or should not be versioned.

Migration Steps

  1. 1. Import — Bring the project via folder, Git or ZIP.
  2. 2. Environment — Install Python/R dependencies from reproducible manifests.
  3. 3. Scripts — Run script-based analysis through the editor/terminal.
  4. 4. Notebook files — Keep `.ipynb` files as project assets; do not assume a dedicated notebook UI unless separately available.
  5. 5. Verify — Regenerate key outputs/plots and compare them.

Where Things Go

Jupyter projectInteractive Shell project
Kernel environmentProject/runtime dependencies
Notebook terminalInteractive Terminal
Markdown/LaTeX outputsProject docs / LaTeX-PDF workflow

Verify

  • Dependencies install.
  • Key scripts run.
  • Plots/data outputs reproduce.
  • Notebook files remain intact.

Common Issues

  • Notebook UI — Interactive Shell does not claim a first-class Jupyter notebook UI unless that feature is separately enabled.
  • Hidden environment state — Capture package versions instead of relying on an old kernel environment.

Last reviewed 2026-09-07.