Skip to main content

Migrating an Existing Project

This page explains how to migrate a user module project created with e Builder to a VSCode development environment.

If you created a new project

If you created a new project, skip this chapter and proceed to Visual Studio Code Setup.

About Accel CLI​

For an overview of Accel CLI, refer to About Accel CLI.

Migration Concept​

The Accel CLI attach command adds the assets required for VSCode development and AI-native development to an existing user module project. It does not affect any existing code or resources under src/.

If a file conflict occurs

If a file to be placed by the attach command already exists in the project, that file is skipped.

Migration Steps​

Navigate to the root directory of the user module project you want to migrate (the directory containing src/ and the e Builder configuration files), then run the following command:

cd /path/to/your-existing-project
bunx @intra-mart/accel attach

Running this command launches the CLI in interactive mode, which will prompt you to select the agent and other options. Follow the on-screen instructions to make your selections. For details on each prompt, refer to Creating a New Project.

About consistency with existing resources

The project name (artifact ID), group name, and version you specify will be used in the assets placed by the attach command. To maintain consistency with the existing resources (module.xml, message.properties), specify the same project name, group name, and version as the existing project.

Assets Added by attach​

After running attach, the following files and directories are added to the project (agent-related files are generated based on your selection):

File / DirectoryDescription
d.ts/TypeScript type definition files for the iAP scripting API (im-BizAPI).
.accel/settings.jsonAccel CLI project settings. Records the selected agent and other options.
package.jsonProject configuration file. Contains dependency declarations and script definitions such as build. Running bun run build executes the build script defined in this file.
pom.xmlMaven project definition file. Defines which libraries to use during build and where to output the artifacts.
settings.xmlMaven settings file. Defines the repositories (sources for libraries) to use.
.claude/Generated if Claude Code is selected. Contains instructions, rules, and skills for Claude Code.
.claude/CLAUDE.mdGenerated if Claude Code is selected. Helps Claude Code understand the project overview.
.github/Generated if GitHub Copilot is selected. Contains instructions, rules, and skills for GitHub Copilot.
.github/copilot-instructions.mdGenerated if GitHub Copilot is selected. Project instructions passed to GitHub Copilot.
.codex/Generated if OpenAI Codex is selected. Contains instructions, rules, and skills for OpenAI Codex.
.codex/AGENTS.mdGenerated if OpenAI Codex is selected. Project instructions passed to OpenAI Codex.

Updating the Template​

For template updates, refer to Updating the Template.

Verification​

Confirm the following two points:

  1. Added assets are present

    Navigate to the project directory and confirm that the main files have been generated.

    Windows (PowerShell):

    ls ('d.ts', '.accel/settings.json', 'package.json', 'pom.xml', 'settings.xml')

    Expected output on success:

        Directory: C:\Users\username\my-project\d.ts

    Mode                 LastWriteTime         Length Name
    ----                 -------------         ------ ----
    d-----        2026/04/27     10:30                bpm
    d-----        2026/04/27     10:30                master
    ...

        Directory: C:\Users\username\my-project\.accel

    Mode                 LastWriteTime         Length Name
    ----                 -------------         ------ ----
    -a----        2026/04/27     10:30          66025 settings.json

        Directory: C:\Users\username\my-project

    Mode                 LastWriteTime         Length Name
    ----                 -------------         ------ ----
    -a----        2026/04/27     10:30            380 package.json
    -a----        2026/04/27     10:30            870 pom.xml
    -a----        2026/04/27     10:30           1085 settings.xml

    macOS / Linux:

    ls d.ts .accel/settings.json package.json pom.xml settings.xml

    Expected output on success:

    .accel/settings.json  package.json  pom.xml  settings.xml

    d.ts:
    bpm  master ...

    If all files are present, the step is complete.

  2. Existing files are not affected

    Use git status or git diff to confirm that existing files under src/ and elsewhere have not been modified (if the project is under Git management).

    git status
If a problem occurs during migration

Refer to the "CLI Execution and Verification Issues" section of Troubleshooting.