I hit a pretty heinous snafu today. I hope someone may
shed some light (beside the worst case that's recurring
in my mind, I am F**d).

Situation is this. We, Company A, Inc., purchased MSCRM
1.0 from Vendor. Vendor licensed MSCRM 1.0 to "Company
A, Inc." During installation of MSCRM 1.0, the
organization unit name "Company A, Inc." caused problems
due to the comma. The fix? "Company A\, Inc."
Delimiting the comma with a backslash remedied the org
unit name problem.

Now for the fun part. MSCRM 1.2 arrived this week.
After prepping for install, I got up the nerve to try the
upgrade. Unfortunately, MSCRM 1.2 installation chokes on
the organization unit name (two forbidden characters,
comma and backslash). It suggests I contact Sales
Operations to have a new registration key issued to a non-
forbidden organizational unit name. Done. So, I have a
new Organization Unit Name and registration key, and I
have a populated database under an old [now forbidden]
Organization Unit Name.

May I somehow alter the Org Unit Name on MSCRM 1.0
without losing data? Worst case, is there an easy way to
dump the data out of MSCRM 1.0 (existing installation),
fix the Org Unit Name and import the dumped data into a
new db? If MSCRM doesn't have this capability
inherently, would Scribe Migrate be able to handle this?

Thanks in advance. I'm in a bind here. MS Support
deferred me to another engineer (first guy's shift was
ending), and they haven't called nor emailed back. Not
promising!