Fabrice, your words frighten me. They make me feel that you probably are not a technical guy, or you are not supported by a good technical team.
A change in a domain name it is a BIG change. Companies have security policies to allow Internet access for their customers. That policies are very restrictive, in most of the cases, specially in the filed of accounting. Thus, financial teams of the company could be permitted not to connect freelly to Internet, but to a particular places. If one of those places is openerp.com, the firewall, proxys, and that kind of technical items allow only connections to openerp.com not to odoo.com, taht would be an unknown site, so probably a non-confident site to connect.
Can you imagine a group of people, the financial team, trying to connect to the regular openerp.com domain to do their work, and getting an error page because the new redirected domain, odoo.com, is not allowed in the connections policies of the company? Can you imagine the "message" they probably would transmit to their bosses? "OpenERP has disappeaerd!", "All our company data, customer data, and activity data, probably lost!"
Even if there is no so restricted policies to connect to Internet, probably there is a BIG impact for a customer to see that openerp.com, the regular site that they visit every day, is redirected to a similar-but-not-the-same site, and with a different name. Probably the customer thinks "openerp.com has been hacked, and redirected to the odoo.com!", or even, "my computer has a virus, that catches all the connections to openerp.com and redirects me to odoo.com, that I don't know, and probably is a fake-domain of pharma-sellers trying to get my attention!"
The solution for this issue is to talk with customers before changing domain, and let them to apply the new policies to allow connections to the new domain, and let them to get information about there will be a new brand name, and let them to report the bosses, and the rest of employees, about the new brand, new look and feel, and new domain.
Another BIG deal. We were testing the use of a personalized domain, just like "www.my-domain.com" pointing to my-domain.my.openerp.com. The alias was running for weeks after we make the changes in our DNS and your technicians did the trick to allow it to work. I say, it worked for weeks ... up to the day of the "not-so-important change". Then the personalized domain was not working at all. We get a "very nice 500 error" trying to visit our www.my-domain.com. Imagine the face of my people, and my customers.
To be honest, at this moment that problem is solved. OK. But it was not working for several days. Isn't it important enough?
I tryed to make a regular download of a backup of my database instance, after the change, and I couldn't. Was it another problem related to the "not-so-ímportant change"? In my opinion, yes, it was. Now it is solved and I could download it, but it wasn't working for several days, also.
One more thing, the price change. Do you really think that one and half month is time enough for a company to react for a billing change like that? If after being noticed about the price change, I decide to go out for my own ERP solution or to another company/service, probably it took me several months to evaluate, decide, contract, and translate all my data, contract learning for the new solution, adapt my technical teams to the new processes, etc.
In a nuthsell, Fabrice, your words, and your actitude, are very, very bad for us, the customers. Everybody can fail, but if customers are telling you that you are making the bad businees, at least, listen to them and offer solutions.