Angelfish includes two utilities for migrating from Urchin to Angelfish:
configmigration: migrates config settings (user accounts, passwords, profiles, filters, log sources)
datamigration: migrates report data from Urchin to Angelfish, using the Urchin 7 API
Step 1 - Migrate Configuration information
From the Angelfish installation directory run ./configmigration with the --help option to view all available flags.
You must point Angelfish at the Urchin installation directory with the --dir flag. This will migrate profiles, datasources, goals, filters, profile groups, users, custom log formats, and schedules.
Here are some important caveats:
- Ecommerce/CPC data is not migrated.
- Funnel paths are not migrated
- Inactive Urchin goals are not migrated.
- The "admin" user account is not moved, since one already exists in Angelfish.
- IT Reports Data is not migrated.
- Geolocation Data will be different - use of different geographic database.
- Average Time on Site will be different. Angelfish calls it "Engagement" and it excludes bounces.
- Log tracking data isn't migrated, which means Angelfish might "re-read" a log file again during processing.
- Migrated visitor data will have different visitor IDs in Angelfish than in Urchin
- Angelfish does not store events.
Step 2 - Migrate Report Data
The datamigration utility is located in the Angelfish installation directory. Please run ./datamigration --help for a full explanation of required and optional flags.
Migrating data from Urchin to Angelfish will take a significant amount of time due to limitations in the Urchin 7 API. The datamigration utility requests data from the Urchin API and recreates a hit for each pageview. Each newly created hit is then processed by Angelfish.
Here is an example of a how a full ./datamigration command might look:
./datamigration --startdate 2011-01-01 --enddate 2011-12-31 --apiuser johndoe --apipass foobar --apiport 9999
Differences from Urchin to Angelfish data
- Visitor IDs are calculated differently in Urchin and Angelfish. After you migrate data from Urchin to Angelfish, the Visitor IDs in any newly-processed data will not match the Visitor IDs in the migrated (historical) data. If you want to maintain Visitor IDs in historical data with newly-processed data, we recommend processing your historical log files in Angelfish (i.e. do not use the datamigration utility).
- Migrated data will not display any information in the Hostname report in Angelfish. Due to Urchin 7 API limitations, Angelfish is not able to migrate the hostname field. The Hostnames report in Angelfish will be empty for any data migrated from Urchin.