CharacterAI to Agnai Migration Guide

Transitioning from **CharacterAI (c.ai)** to **Agnai** represents a move from a closed, proprietary cloud service to an open, feature-rich roleplay platform. While CharacterAI encourages long, monolithic definitions, Agnai thrives on a more modular and structured JSON approach that facilitates advanced features like group chats and world-shared lore.

1. Analyzing the "Definition" Schema

CharacterAI primarily stores character logic in a single Definition (Advanced) field. This often contains a chaotic mix of descriptive traits, world-building, and dialogue examples. Agnai uses a more specialized JSON model.

2. Working with Group-Chat Dynamics

Agnai is designed for multi-user interactions. Standard CharacterAI personas are often authored with a strict 1-on-1 text completion focus. Text is copied across as written (see "What this converter changes" below), so review the result in Agnai and adjust any wording or formatting you want to change. We prioritize the preservation of the character's core persona and description, ensuring they are mapped to Agnai's definition blocks to maintain behavioral integrity even in complex, multi-actor scenes.

3. Dialogue and Greeting Migration

We extract the "Greeting" from CharacterAI and map it to Agnai's first_mes field. This normalization is critical because different inference backends interpret dialogue cues differently. Text is copied across as written (see "What this converter changes" below), so review the result in Agnai and adjust any wording or formatting you want to change.

4. Privacy and Data Sovereignty

We believe that your characters are personal creative assets. By using a "Zero-Server" architecture, we perform the entire extraction and mapping process within your browser's RAM. Your intimate character details and creative backstories are never transmitted across the open web. This provides a secure, private bridge for users who want to transition their digital creations to a more private, local-first or self-hosted roleplay experience.

5. Identity and Metadata Fields

Agnai benefits from characters that include descriptive tags and versioning info. The name, description, personality, scenario, first message and example dialogue are written to the Agnai JSON; tags and version metadata are not generated. This facilitates better character management and ensures your characters are ready for advanced Agnai features like "Lore Sharing" and "Campaign Orchestration."