Migration Overview

Abolitus is designed to make migration practical, not ceremonial.

If you already have real characters, old chats, or worldbuilding material in another roleplay tool, the best starting point is usually to import what already works and then clean it up inside Abolitus.

For most users, migration is not about nostalgia.

It is about preserving momentum.

You may already have:

• characters with a voice you like,
• chats with emotional continuity,
• lore material that took weeks to stabilize,
• and workflow habits built around another client.

The goal of migration is to move those assets without forcing you to restart from zero.

What You Can Usually Bring Over

In most cases, the main import targets are:

• character cards,
• chat histories,
• and lore or world-info material.

The exact quality of the transfer depends on how standardized the original format is and how much of the original platform's behavior came from invisible defaults rather than from the stored data itself.

What Happens After Import

Imported data becomes part of your local Abolitus workspace first.

That means:

• you can review it before trusting it,
• you can edit it like native Abolitus content,
• and it only becomes part of cross-device continuity if you later choose a backup or sync path that includes it.

That last point matters.

Importing something into Abolitus is not the same thing as publishing it to a server-side account record.

The import lands in your working local environment first.

Why Migration Sometimes Feels Worse Before It Feels Better

Migration can temporarily feel disappointing when users expect the old platform's invisible defaults to transfer automatically.

But what usually happens is simpler:

• the data transfers,
• the surrounding environment changes,
• and the first live scene reveals which parts of the old behavior were really card data versus platform behavior.

That is normal.

Migration is not just import. It is import plus re-tuning.

What Usually Needs Review After Migration

Even a successful import should be treated as the beginning of a tuning pass.

After importing, check:

• whether character tone still feels right,
• whether greetings still land the way you expect,
• whether lore retrieval is too weak or too noisy,
• whether the new route is more or less aligned than the old one,
• and whether sampler or wrapper choices need adjustment.

Many "bad imports" are actually good imports landing inside a different prompt and routing environment.

Recommended Migration Order

If you are moving a serious setup, this order works well:

1. Import characters.
2. Import a few representative chats.
3. Import lore.
4. Test one live scene.
5. Clean up personas, wrappers, samplers, and routing after the import succeeds.

This order keeps the debugging surface small.

If you import everything at once, it becomes much harder to tell whether a problem came from the data, the route, the prompt environment, or your new workflow habits.

Do Not Expect Perfect One-to-One Behavior

Even when import succeeds, two platforms may still feel different because:

• their prompt defaults differ,
• their model routes differ,
• their lore retrieval logic differs,
• and their UI habits differ.

Migration is best treated as a strong starting point, not a promise that every scene will feel identical on the first turn.

A Good First Migration Session

If you want the smoothest possible first day, do this:

1. Import one favorite character.
2. Import one chat that represents the tone you care about most.
3. Start a short live scene.
4. Fix wrapper, route, and sampler mismatch before importing more.
5. Only then bring over the rest of the archive.

That approach preserves quality and prevents a large messy import from turning into a vague, frustrating troubleshooting session.

Choose the Right Migration Page

Use this section based on what you are actually bringing over:

• Character Cards for general card import,
• SillyTavern for heavier local-roleplay archives,
• JanitorAI if you are moving from a hosted roleplay workflow.