For future review and auditing purposes, a log of migrations should be maintained by Wildebeest. This would be best done in a structured format like XML so that various types of information can be collated in a machine readible format.
The use case would be to have the migration logfile continually being updated by Wildebeest for each migration that it performs. The log file could then be fed back to change management or issue tracking tools for future review and auditing.
Possibly rather than continually adding to a single log file, Wildebeest should write a separate log file for each migration.
A Migration Log Viewer tool should be provided to enable easy reading of log files, and if separate log files are used the tool should also be able to collate multiple log files to provide a single view of the history of a stateful resource.