Practical guide

Move a setup from TikFinity

Map the tools you use, rebuild one workflow at a time and avoid duplicate reactions.

What you will be able to doYou can decide which parts to move, which to keep and how to test without triggering the same event twice.

Before you start

  • A list of the TikFinity features you actively use.
  • Screenshots or notes of your settings, with private credentials and URLs redacted.

Inventory the actual workflow

  • List each source: full overlay, individual alert, goal, game, TTS and sound output.
  • Record each event’s trigger, audience, cooldown, response, media and sound level.
  • List external dependencies such as Streamer.bot, a local Event API client, a game plugin or mobile companion.
  • Record the account and device that own the setup. Do not assume settings or local sound files move between apps.

Map only the features that exist

Compare your list against iTok’s reviewed feature matrix. iTok can suit a show that prioritizes a shared visual editor, separate widget links, Heart Me and jar presentation, built-in Connect Four and coordinated opening and closing graphics.

TikFinity has documented strengths in its local Event API, Streamer.bot and game integrations, points economy and native mobile companion. Those can be decisive requirements. iTok’s current chat-posting bridge may still depend on TikFinity.

Rebuild one workflow at a time

  1. Start with one noncritical widget in a separate preparation scene.
  2. Recreate the appearance and source dimensions, then the event conditions and audio route.
  3. Test its saved picture and sound deliberately. Check real event delivery before relying on it live.
  4. Disable the old reaction for that event before enabling the replacement on the main scene, so both apps do not respond unintentionally.
  5. Keep the known working setup available until the replacement covers the actual show requirements.

Plan for setup, not automatic conversion

iTok does not currently import a TikFinity configuration automatically. Reusing a name or finding a similar control is not proof that its behavior, limits or data model are identical.

Compare costs for the voices, platform and tools you actually need. The iTok beta invitation and optional TTS credits are separate questions. TikFinity desktop/browser and mobile plans also have separate limits. Use the current pricing pages rather than an old screenshot.

These instructions describe the reviewed iTok beta. Provider access and physical-device behavior still need to be checked in your setup.

Read product updates