Migrating from Codex
If your team already has projects in Codex (the older VS Code extension, backed by GitLab), those projects can be brought into Aquilla.
How the import works
Section titled “How the import works”Migration is a one-way, continuous import:
- Aquilla connects to your GitLab project, reads its history, and replays it into Aquilla so your cells and their history come across faithfully.
- It’s idempotent — running it again on the same source safely skips work that’s already been imported, so a re-run won’t create duplicates.
What you’ll see while it runs
Section titled “What you’ll see while it runs”You can keep the project open while it imports:
- New cells appear in real time as they’re brought in.
- If the import touches cells you’ve already edited in Aquilla, those particular updates won’t appear live — close and reopen the project to see them. This is a known limitation during alpha.
Cutover: Aquilla becomes the source of truth
Section titled “Cutover: Aquilla becomes the source of truth”Once a project is imported, Aquilla is the single source of truth for it. The GitLab side is no longer kept in sync — from cutover onward you translate, review, and collaborate in Aquilla. When you need your work elsewhere, use Export.
Who runs migrations today
Section titled “Who runs migrations today”During alpha, migrations are run by the Aquilla team on your behalf — they backfill customer projects for you. Self-service migration, where a project maintainer imports their own GitLab project, is planned for a later release.