Sure, just store it that way, and make sure the output is converted to UTF8 at every point where a modern system is involved (envelope and letter printing, stat

Sure, just store it that way, and make sure the output is converted to UTF8 at every point where a modern system is involved (envelope and letter printing, statement printing, customer website, internal customer support tools, internal anti fraud and audit tools). Also convert input from UTF8 to EBCDIC at every point a user or employee can type into a modern keyboard/OS. Eg searching customers by name. Teach employees on inputting characters. Are we going to allow all unicode characters? Will they be able to find records if the customer doesn't give the diacritics in one context such as phone? Also some routine tasks will be done using a mainframe terminal which doesn't support displaying these characters. More training there as they will just display the UTF-EBCDIC version of the field. Are there connections like tax agencies, credit reporting agencies, other banks, Visa/Mastercard, and what character sets do they support? We always sent them ASCII CSVs via FTP and everybody who understands it no longer works here.