Moving a character between Candy AI and DreamCompanion is really moving your brief: adulthood, traits, appearance anchors, and the current scene. The apps will not share chat memory. Portability means you control the text file; it does not mean identical replies.

Export what you own

  1. Write or update the offline card (identity + boundaries + scene).
  2. Note which app-held extras you cannot export (generated images, in-app memory, voice samples).
  3. Decide the destination priority: style fork first (Candy review) or personality paths first (DreamCompanion review).

Candy → DreamCompanion

If you began on Candy for anime-or-realistic exploration, freeze the look description that worked (hair, ears, one outfit). In DreamCompanion, place appearance and personality in the matching fields when available, then run the week-one hobby recall check. Soft start: DreamCompanion.

DreamCompanion → Candy

If the voice is strong but you want faster visual iteration, carry the same adult identity into Candy’s creator, keep one outfit constant across two scenes, and watch token-priced media separately from chat. Soft start: Candy AI.

Dual CTA decision

Choose DreamCompanion when the greeting tone and custom prompt matter most; choose Candy when the aesthetic fork and image experiments matter most. You can keep both accounts temporarily, but keep one canonical offline card so you do not invent conflicting biographies. Deeper billing notes live in the reviews linked above; privacy hygiene is in our companion privacy brief.

Editorial scope

YukiGF migration craft, September 10, 2026. Documentation-led; no cross-app memory claim.