The yfs.api.history.disable.colony.<colony_id> property allows you to migrate transaction data for individual colonies in a sharded deployment before migrating the history data. When performing a colony-by-colony upgrade, you can use this property to migrate data without completely shutting down the production environment for the individual colonies. Use the yfs.api.history.disable property when you are migrating all colonies; use the yfs.api.history.disable.colony.<colony_id> property when you are migrating individual colonies.
If you are using the yfs.api.history.disable.colony.<colony_id> property to migrate the transaction data before the history data for individual colonies, follow these steps: