Migrating from SillyTavern

SillyTavern is one of the most natural starting points for migration because many users already have mature character libraries and long-running chats there.

It is also one of the easiest places to underestimate migration complexity. SillyTavern users often have years of accumulated cards, lore, presets, macros, and model habits layered together.

The good news is that the assets usually transfer well enough to preserve momentum. The part that needs care is behavioral tuning after the import.

What You Can Migrate

The main targets are:

• Character cards.
• Chat histories.
• World Info or lorebook material.

If your setup is especially large, start with the material that still matters in active use rather than bulk-importing your entire archive on day one.

Character Cards

Character cards are usually the easiest part of the move.

If your library already uses standard PNG or JSON cards, bring those in first and verify that each character still feels correct before you import everything else.

Focus your first review on:

• character voice,
• greeting quality,
• scenario framing,
• and whether the imported card still produces the same social tone in the first few turns.

If those pieces feel right, the migration foundation is usually solid.

Chat Histories

For old chats, export the chat history from SillyTavern and import it into the matching character flow in Abolitus.

After import, check:

• Message order.
• Speaker continuity.
• Whether the imported chat still feels like the same scene.

Do not judge success only by whether the file imported. Judge it by whether the resumed scene still feels coherent when you continue it live.

That is the real migration test.

World Info and Lorebooks

This is where the migration may feel different rather than simply identical.

SillyTavern users often think in terms of keyword-first world info. Abolitus can still work with imported lore, but the memory workflow is broader than exact string matching alone.

That means imported lore can remain useful even after you stop managing it the exact same way you did before.

In practice, this means you should review imported lore for:

• duplicated facts,
• overly narrow trigger wording,
• references that only made sense inside old prompt conventions,
• and entries that are too long to stay high-value.

Migration is a good time to simplify bloated lorebooks that grew around old client limitations.

Recommended Strategy

Do not import your entire archive blindly and assume it is all equally important.

Start with:

1. A few important characters.
2. One or two representative chats.
3. The lore that those scenes actually depend on.

Once that smaller sample works, scale up.

What Usually Needs Retuning After the Move

If a character feels different after migration, the cause is often one of these:

• a different model route,
• a different wrapper preset,
• different sampler behavior,
• different lore activation pressure,
• or a different context budget.

That is why you should tune behavior after import instead of assuming the imported data itself is wrong.

The Right Mindset

Think of SillyTavern migration as moving assets into a cleaner control environment.

You are not only trying to preserve what you had. You are also trying to gain a workflow where the reasons behind good or bad behavior are easier to inspect and adjust.