legacy-type-mapping

Schema evolution during class renaming or retyping is managed by applying explicit CSV mappings or custom handlers. This approach preserves data compatibility and ensures smooth evolution of storage formats without rewriting stored files.

Migrating data for splitting fields or restructuring nested objects requires implementing custom legacy handlers. These handlers process complex transformations that simple field mapping cannot cover, ensuring accurate data translation during schema migration.

Yes, you can use CSV files to apply explicit field mappings during data migration. This skill supports loading explicit CSV mappings to define how classes and fields are renamed, retyped, or relocated across the storage format evolution.

Dropping classes or deleting fields without breaking existing stored data requires following specific schema migration guidance. This process ensures that removal operations maintain data integrity and compatibility with previously persisted storage formats.

You need a custom handler instead of standard field mapping for schema refactoring when facing complex transformations like splitting fields or handling nested object restructuring. Standard CSV mappings handle simple renaming and retyping, while custom handlers manage intricate structural changes.