Network Migration: Urchin to Angelfish

This article describes how to migrate Urchin data to an Angelfish instance on a separate server.

Before You Begin, You'll Need:

  • Access to the Urchin application directory
  • The IP address of the Urchin server
  • Network access to the mySQL or Postgres instance used by Urchin


When migrating from Urchin to Angelfish, there are two utilities to use:

Migrates config settings (user accounts, passwords, profiles, filters, log sources) from Urchin to Angelfish.


Migrates report data from Urchin to Angelfish, using the Urchin 7 API.
Alternatively, you can reprocess log files in Angelfish instead of using this utility.

The configmigration utility is intended for same-server migration, but you can "trick" the utility into connecting to a remote Urchin instance. Here's how:

1) On the Angelfish server, create a new directory called "urchintmp"

This directory can be located anywhere in the local filesystem, e.g. C:\urchintmp or /home/agf/urchintmp

2) Copy 3 directories from the Urchin server to the Angelfish server

The following Urchin application subdirectories need to be copied from the Urchin server to the directory on the Angelfish server created in step 1:

  • /bin/
  • /etc/
  • /lib/

These subdirectories are located beneath the Urchin root folder on your Urchin server.

3) Update urchin.conf in urchintmp/etc/

If using Windows, use wordpad or a text editor - don't use notepad!

The newly-copied /etc/ folder in urchintmp contains a file called urchin.conf - you'll want to edit this file and update the setting for "SQLServer".

Find this line:

SQLServer: localhost

and replace "localhost" with the IP address of the Urchin server.

Once complete, the section should look something like this:

SQLType: mysql
SQLUsername: urchin7
SQLPassword: itsasecret
SQLDatabase: urchin7
SQLPort: 3306
SQLSocket: /var/lib/mysql/mysql.sock


By default, remote access is disabled in mySQL.  You may need to enable remote access AND disable mySQL's hostname lookup - please refer to the following articles:


If you use PostgreSQL with Urchin, the settings will be a bit different - please use the above example as a guide.

(open a support ticket if you get stuck)

4) Run configmigration and reference the local directory

Windows example:

configmigration --dir C:\urchintmp

Linux example:

./configmigration --dir /home/agf/urchintmp

If the settings are correct, the configmigration utility will access the local copy of urchin.conf and use the settings to migrate config data from the mySQL / Postgres instance on the remote Urchin server.

Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.