Migration
Migrate from copy-ai to claude.
1 documentation-derived translation pattern — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Move Copy.ai Chat work into a Claude Project. Upload each Infobase entry (brand guidelines, value props, positioning, product specs) as the Project's knowledge files, and put your standing voice/format rules into the Project's custom instructions, so Claude has the same grounded context Copy.ai referenced via '#'. Since Copy.ai Chat already exposes Anthropic Claude Sonnet models, prompts that worked there should transfer closely; recreate your pre-made GTM prompts as project instructions or reusable messages.
Gotchas
- Warning: A Claude Project applies its uploaded knowledge to every conversation in the project rather than letting you inject one named '#' snippet per prompt, so split a large Infobase across multiple Projects if it exceeds the knowledge limit.
- Warning: Copy.ai's bulk Table view (run a workflow over a CSV of rows) has no equivalent in a Claude Project; high-volume, repeatable runs that depended on Workflows must be rebuilt manually or kept on Copy.ai rather than moved to Claude chat.