Changing a field type is a significant configuration change that can have downstream impacts. When converting from Text to Picklist, a Platform Administrator must be aware of two critical consequences:
* List View Deletion:Any list views that use that specific custom field as a filter will be automatically deleted or the filter will be removed. This happens because the filter logic for a text field (which uses operators like "contains") is fundamentally different from a picklist (which uses "equals").
* Automation Impact: Assignment rules, escalation rules, and validation rules that reference the field may be disabled or function incorrectly. Because these automations rely on specific text strings, changing the field to a picklist requires the administrator to manually review and update the logic to ensure it aligns with the new picklist values.
Option A is incorrect because Salesforce does not automatically update code references. Option C is incorrect because data loss can still occur if existing text values do not exactly match the new picklist entries.