...
- A Large number of records: a larger the number of records makes for a better the use case for a migration. However, a bulk update can also be used to easily update a large number of records, so having many records by itself does NOT make a migration the recommended tool.
- Each record needs different data set: When the number of records is large, a bulk update makes your life easy – you can easily, say, update 500 grants such that their Project Title becomes "Test." However, if each grant needs a different project title set on it, e.g., a bulk update is NOT the correct tool as a bulk update can only set data in a field to 1 specific thing for all records. A migration allows you to set set different data for each record that is being touched.
- The data that needs to be set is not multiple-response: When using the migration tool, multiple-response items CANNOT be updated correctly; instead of setting 2 different values within 1 field, the migration concatenates the two values into 1 value and turns that 1 value into a new option available for selection with that multiple-response field. If you need to set different data on a large number of records for a multiple response item, your only real option is to use Fluxx's API to set the multiple response data.
...