Migration — Inventaire de retrait du Studio legacy
Ce qui n’est volontairement pas copié octet pour octet dans Orbit, et pourquoi.
Frozen comparison source:
- repository:
BoostEcom/studio.boostecom.app - baseline:
94d051cfd02e5ef0c7b721a56df700e50481de4c - successor:
BoostEcom/orbit.easyconnector.app
This inventory explains what is intentionally not copied byte-for-byte into Orbit. A missing legacy path is not automatically missing functionality: route groups, product names, tests and render assets were deliberately reorganized during the migration.
Classification
| Legacy area | Status in Orbit | Retirement action |
|---|---|---|
src/app/(studio)/* routes | Replaced by src/app/(dashboard)/*; URLs remain product URLs such as /studio, /brain, /members | Discard legacy paths |
| Brain, Creative Studio, auth, API/MCP, DB, engine, connectors | Migrated and covered by current build/quality/E2E/Remotion gates | Orbit is canonical |
Legacy BoostEcom Remotion film (film/boostecom/*) | Intentionally not imported; it is a historical BoostEcom marketing film, not the Creative Studio render engine | Archive only if the historical film matters |
| BoostEcom partner logos / hub artwork | Not part of Orbit product runtime | Archive or discard |
products/boostecom/* design/deriver/facts | Replaced by Orbit product data and products/orbit/design/orbit.DESIGN.json where render tokens are needed | Discard legacy product snapshot after archive |
| Remotion core engine | Migrated selectively: ProductFilm, UiShot, templates, capture, render, QC, callback, Postiz, TTS/mux and real-media E2E remain in Orbit | Orbit is canonical |
| Old Remotion skills/reference bundle | Not required by runtime or CI | Reinstall/reacquire from upstream if wanted; no dedicated repo required |
| Old Remotion music/SFX legal record | Replaced by Orbit-specific packages/remotion/ATTRIBUTION.md and an enforced licence test | Orbit is canonical |
| Old architecture/ADR/runbook docs | Migrated, then moved to the documentation repository (2026-10): the engineering docs (architecture, StudioHost contract, connectors, MCP/OAuth, visual context, runbooks, the ten ADRs, roadmap, development guide, migration records) were first rewritten for Orbit at the same paths, then moved to docs.easyconnector.app (protected pages of this repository). The application repository holds no prose documentation and no docs/ folder; there is one ADR series (the former application ADRs 0001 to 0010 are now ADR-0011 to ADR-0020). Public product docs are in the same repository | Documentation repository is canonical. The old migration plans (carte-de-migration.md, orbit-context-os.md, plan-final-migration-studio.md) remain archive-only |
| Old unit/integration test file layout | Not copied byte-for-byte; current Orbit tests plus build, quality, E2E and Remotion gates are canonical | Do not create a separate test repo |
design-drift.yml | Coupled to the old BoostEcom design derivation | Do not port as-is; create an Orbit-specific drift check later if needed |
Legacy engine README / fixture README, Remotion README and packages/remotion/references/*.md | Migrated and rewritten for Orbit (2026-10): packages/engine/README.md, packages/engine/src/generation/fixtures/README.md, packages/remotion/README.md, packages/remotion/references/{captures,elevenlabs,formats,hooks,motion-language,ops,postiz-video}.md (Orbit error messages point to them). Content about the retired marketing film and the parent-platform capture bridge was dropped | Orbit is canonical; references/hume-exit.md and docs/README.plateforme.md stay archive-only |
CLAUDE.md | Tool-specific legacy repository instruction | Discard |
stray file hich is still read while this key is unset.# | Garbage artifact | Discard |
Items worth archiving before deleting the old repository
If historical preservation matters, keep a read-only archive/tag containing:
packages/remotion/film/boostecom/;packages/remotion/public/partners/;products/boostecom/;- the old migration plans (the architecture/ADR/runbook docs now live, rewritten, in Orbit);
- Git history and old pull requests.
None of those should be moved into the active Orbit runtime merely to keep them available.
External state is not contained in Git
Deleting the legacy repository does not migrate or validate external systems. Before deletion, independently confirm:
- Orbit's Vercel project has the intended production/preview environment variables and domains;
- the dedicated Orbit Postgres/Neon database contains the required production data and committed migrations have been deployed;
- Blob assets referenced by Orbit's database still exist;
- GitHub environment/repository secrets needed by
render.yml, database deployment and callbacks are configured on the Orbit repository; - Resend, AI Gateway, ElevenLabs, Postiz and connector credentials that Orbit still uses are owned/configured by Orbit rather than the legacy repository;
- any external webhook or OAuth redirect URL points at
orbit.easyconnector.app.
Deletion policy
Archive the legacy repository first. Keep it read-only through at least one complete production cycle of Orbit (auth, Brain, Creative Studio generation, render callback, MCP/API and a database migration). Delete it only after that cycle succeeds and the external-state checklist above is confirmed.
Was this page helpful?