Move your team from Claude to Copy.ai.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Copy.ai — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Claude is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
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.
- 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.