Migration
=========

IMMP comes with limited support for migrating from another bot framework.

hangoutsbot
-----------

The **immp-migrate-hangoutsbot.py** script will read a bot's config and memory JSON files, and
produce an initial IMMP config file and database::

    $ immp-migrate-hangoutsbot.py \
        ~/.local/share/hangoutsbot/config.json \
        ~/.local/share/hangoutsbot/memory.json \
        data/config.yaml \
        apsw:///data/data.db

:ref:`admins/plugs:Hangouts` will be configured as standard.  :ref:`admins/plugs:Slack` will be
added from a SlackRTM plugin config, and :ref:`admins/plugs:Telegram` from telesync.  Any bridged
chats will be recreated using :ref:`admins/hooks:Sync`.

A :ref:`admins/hooks:Commands` handler will be added with ``/bot`` as the command prefix.  Any
tl;dr entries will be copied to :ref:`admins/hooks:Notes`, for the synced channel if synced, else
the Hangouts chat.

For each user with a nickname set, their Hangouts user will be added to a :ref:`admins/hooks:Local
identity` hook.  If profile-synced with SlackRTM or telesync, the corresponding Slack/Telegram
links will be added to their identity.

.. note::
    Each identity will be created without a password -- users will need to use the **id-password**
    command to set one before confirming any further identity links.