/migrate-company
/migrate-company moves the company information from an old single profile file into the six company context files that AI Business OS has used since version 2.0. Claude splits the old file section by section, asks you to fill in any areas the old file covered thinly and cleans up once you approve the result.
/migrate-company stays the same when PRIMA Project Management is installed.
When to Use It
Section titled “When to Use It”You need this command only if your workspace started on AI Business OS version 1. Those workspaces kept all company information in one file called CLIENT_PROFILE.md, at the workspace root or in .claude/. A workspace installed from version 2.0 onwards already has the six company files and has nothing to migrate.
You may be prompted to run it. When /update finds a CLIENT_PROFILE.md, it tells you to run the preparation script and then this command.
How to Run It
Section titled “How to Run It”- Type
/migrate-companyin the message box at the bottom of the Claude Code panel and press Enter. - Answer the questions Claude asks about any thin areas, or choose to leave them for later.
- Review the summary of the six files and approve it, ask for a revision or reject it.
What It Does
Section titled “What It Does”Claude first checks and prepares the migration.
- Checks the state of the migration. Claude runs
bash Infrastructure/Scripts/migrate-company.sh --check, which reports and changes nothing. If there is no old profile and no migration in progress, Claude tells you there is nothing to do and stops. - Prepares the files. If the old profile has not been prepared yet, Claude runs
bash Infrastructure/Scripts/migrate-company.sh. This script archives the old profile to.claude/engine-backups/company-migration/with a timestamp and moves a working copy to.claude/company/CLIENT_PROFILE-legacy.md. It also makes sure the six company files exist and writes.claude/company/.migration-pending.jsonto record the migration in progress.
Claude then moves the content and checks it with you.
- Splits the content. Claude reads the working copy from start to finish and copies each section into the right company file. It keeps your tables, lists and headings as you wrote them, because the split moves your words and does not rewrite them.
- Finds the thin areas. Claude checks each of the six files for areas where the old profile had little or nothing, and offers a walkthrough for each one.
- Asks for your review. Claude lists each file with where its content came from and how many lines it holds.
- Cleans up and commits. After you approve, Claude removes the working copy and the migration record, then commits the company files and the archive.
Where Each Section Goes
Section titled “Where Each Section Goes”| Section in the old profile | Company file |
|---|---|
| Organisation overview, brief description, products and services, pricing notes, competitors and market position | overview.md |
| Key contacts, external advisors and coaches, approval process | team.md |
| Target audiences | audiences.md |
| Voice and tone in full, the prose style parts of working preferences, and the quality checklist | voice.md |
| Industry terminology, regulatory and compliance considerations, common document types | industry.md |
| Brand guidelines, including visual identity, signature phrases and document templates | brand.md |
Claude places the few sections that do not fit the six files as shown below.
| Section in the old profile | Where it goes |
|---|---|
| Technology context | A new file, .claude/company/technology.md |
| Cloud storage | A new file, .claude/company/cloud-storage.md |
| Background notes on a named person | Added to team.md as notes on key contacts |
| Current priorities | Added to overview.md under a Current Priorities heading |
| Profile maintenance | Left out, because the new files have their own upkeep |
The Thin-Area Walkthrough
Section titled “The Thin-Area Walkthrough”Older profiles often say little about voice, brand or audiences. When Claude finds a thin file, you choose one of two options.
| Option | What happens |
|---|---|
| Leave as it is | Claude moves on and you can edit the file later |
| Walk me through it | Claude asks numbered questions one at a time, waits for each answer and then writes the file |
The questions depend on the file.
| File | What Claude asks about |
|---|---|
voice.md |
Your tone, formality, UK or US English, jargon, acronyms and anything you never want written |
brand.md |
Your colours, fonts, logo location and taglines |
audiences.md |
Your primary audience, what it needs and any secondary audiences |
Approving, Revising or Rejecting
Section titled “Approving, Revising or Rejecting”| Option | What happens |
|---|---|
| Approve | Claude cleans up and commits |
| Revise | You name a file and Claude edits it |
| Reject | Claude runs bash Infrastructure/Scripts/migrate-company.sh --rollback, which restores the old profile to .claude/CLIENT_PROFILE.md from the archive and removes the migration record. It does not undo the changes already written to the six company files, and it leaves the working copy in .claude/company/. Use git to restore the company files if you want them back as they were, then run the command again |
What It Reads and Writes
Section titled “What It Reads and Writes”| File | Read or write |
|---|---|
CLIENT_PROFILE.md or .claude/CLIENT_PROFILE.md |
Read, then archived and moved by the preparation script |
.claude/engine-backups/company-migration/ |
The dated archive of the old profile is written here |
.claude/company/ |
The six company files are written, and technology.md and cloud-storage.md when needed |
.claude/company/.migration-pending.json |
Written by the preparation script and removed at clean-up |
Example
Section titled “Example”/migrate-company**Migration walkthrough: voice.md is thin**
The legacy profile had one paragraph on voice and tone. The file now contains:
Tone: Professional but approachable.
**Options:**- **A:** Leave as-is — you can edit later- **B:** Walk me through it now
Which do you prefer?