function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
thesunloverthesunlover 

Rebranding best practices

Hi all,

We are rebranding the company due to a merge with another one and I wanted to check if some of you has encountered with the same case in the past.
What options for rebranding do we have in the SF?
Are we able to update the Namespace?
Are we able to update the owner of the package?
what else to expect?
Is it better to start a new managed package and create a 2nd copy with the new name and namespace?

Any help would be appreciated.
Thank you in advance

BR
HarshHarsh (Salesforce Developers) 
Hi,
I need to get some things more clear before I can fully respond to your question.
Q1) Rebranding means changing the name of the org or changing the domain name or it will remain the same?
Q2) Do you want to know about packages and namespace after changing the domain name?

 
 
thesunloverthesunlover
Hi Harsh, 
Thank you for taking the time. 
Some general information 
Our rebranding is in terms of our 1GP managed package and the namespace we have released the package. We have only Dev Edition orgs. 
So
Q1) we could change it, however it is a developer edition. If it helps somehow to change the namespace, however I have concluded that it's not possible to change the namespace associated with the non Dev Hub org.
Q2) sure, will be nice to know in case we have a production one someday.