Migrating from Codex

If your team already has projects in Codex (the older VS Code extension, backed by GitLab), you can bring them into Aquilla.

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.
• Running it again on the same source safely skips work that’s already been imported, so a re-run won’t create duplicates.
• A re-run also cleans up on your side: a cell deleted back in Codex is retracted from Aquilla too, so re-migrating stays in sync in both directions.

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, a known limitation for now.

Cutover: Aquilla becomes the source of truth

Once a project is imported, Aquilla is the single source of truth for it. GitLab no longer syncs. From cutover onward you translate, review, and collaborate in Aquilla. When you need your work elsewhere, use Export.

Who runs migrations today

For now, the Aquilla team runs migrations 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.

Moving from Codex?

If you’re coordinating a move from Codex, talk to your Aquilla contact so they can schedule the import. Have your GitLab project details ready.