Split a company

There's no dedicated "split company" command, but the Export & Import flow gets you there in two passes.

Export the source company twice, scoped to what each new company should own — the --skills <slugs> and --projects <names> flags do exactly the slicing you're after:

paperclipai company export <src-id> --out ./company-a \ --include company,agents,projects,skills \ --skills skill-a,skill-b --projects project-1

paperclipai company export <src-id> --out ./company-b \ --include company,agents,projects,skills \ --skills skill-c,skill-d --projects project-2

Import each as a new company:

paperclipai company import ./company-a --target new --new-company-name "Company A" paperclipai company import ./company-b --target new --new-company-name "Company B"

A few things to keep in mind:

Always run --dry-run first to preview what will be created. Imported agents always start with timer heartbeats disabled — intentional, so you can review and budget before anyone starts spending. Secrets are scrubbed from exports (API keys, tokens). The package declares which env vars the agents need; you re-attach the values after import. "Knowledge" portability depends on adapter. For claudelocal, codexlocal, etc., it's the working directory and skills — fully portable. For hermeslocal, the on-disk memory store is not migrated. If you have a Hermes agent whose memory matters, have it write a summary to a skill or task comment before exporting. Once both new companies are stable, soft-delete the original from the admin surface to avoid drift.

Full reference: Export & Import (/docs/power-features/export-import).

What are you trying to separate — by team, product, or adapter mix? Happy to sketch a more concrete plan if you share the structure.