Your class will have a data base table rule which contains table name corresponding to it.
You can change table name there.
For instances to be moved to new table i guess you can export the instances before and can import back after remapping.
If you have other customer classes mapped to pr_other and you've added properties to these customer classes and optimized them (hence generating another DB column), then you may not need that column for your new class.
As a safeguard you may want to do all columns, but you may want to look more closely at the ones that don't start with pz, py, or px.
I'm sure your database software may have some feature(s) which allow you to clone a table structure.
If not, hopefully they will allow you to see the SQL for the pr_other. The re-run this specifying your table name, and not forgetting to rename and indexes to the appropriate format for the new table.
Then after this, you should be able to follow Arun's suggestion from earlier, and hopefully all is done.