Migrating from JanitorAI
Bring JanitorAI-style characters into a more controllable local-first workflow.
Many users come to Abolitus because they want more control than a hosted roleplay platform usually gives them.
That makes JanitorAI migration less about copying the exact old environment and more about preserving the parts that matter while gaining more transparent control.
In other words, the import is not only a data transfer.
It is usually a workflow upgrade.
What Usually Transfers Best
The most transferable part is the character definition itself.
In practice, that means imported cards can usually preserve the essential identity of:
- personality,
- scenario,
- greeting,
- and core descriptive framing.
If a JanitorAI character already had a strong identity on the page, that identity usually survives the move better than users expect.
What Usually Does Not Transfer Perfectly
What users often miss is that a platform feeling is not made only from the card.
It is also made from:
- route choice,
- hidden or implicit wrapper behavior,
- provider alignment style,
- sampler defaults,
- and the surrounding workflow.
That is why a migrated character can be fundamentally correct while still feeling "off" on the first live turn.
The Right Question After Import
The right question is not:
"Did the import work?"
The better question is:
"Which part of the old behavior came from the card, and which part came from the old platform?"
That distinction saves a lot of frustration.
Many "bad imports" are actually good imports landing inside a different route and prompt environment.
What to Review After Import
After import, expect to review:
- wrapper choice,
- sampler choice,
- persona fit,
- lorebook support,
- and route selection.
If the character's emotional identity survives but the tone feels wrong, the fix is often in that surrounding stack rather than in the imported card itself.
Recommended Migration Approach
- Import one character.
- Test the greeting and a short live scene.
- Choose a wrapper preset that fits the tone you want.
- Confirm the route is appropriate.
- Adjust samplers only after the wrapper and route feel correct.
If you are testing multiple imported characters, repeat that loop with one strong representative sample before moving the rest of your library.
That keeps the debugging surface small.
What You Gain After the Move
The main benefit of migration is not just ownership of the character file.
It is the ability to control the rest of the scene stack directly instead of guessing at invisible hosted defaults.
That includes:
- choosing your own route,
- deciding how strict or loose wrappers should be,
- managing lore and persona pressure more clearly,
- and keeping the workspace local-first instead of surrendering everything to a hosted platform.
A Good Expectation to Keep
The first post-migration scene may not feel identical to the original platform, and that is normal.
What matters is whether the imported character still has the same core identity and whether Abolitus gives you enough control to recover or improve the behavior quickly.
If the answer is yes, the migration was successful even if the first tuning pass is not finished yet.
Related Pages
- Read Character Cards for the general import rules that are not specific to JanitorAI.
- Read Migration Overview if you are moving chats and lore as well as characters.
- Read Prompt Wrappers and Jailbreaks if the main problem after import is tone or refusal style rather than raw card fidelity.