Hello Everyone- I am currently working with a SuiteBundle utilized by over 100 clients, and I've chosen to transition it from its existing Bundle format to the SuiteCloud Development Framework (SDF). However, I would like to retain the original bundle ID during this process. As I am somewhat uncertain about the implications of SDF migration, I am seeking assurance that this change will not negatively affect our clients. Ideally, I would prefer not to involve them in this process. Are there any critical factors or considerations I should be aware of during this migration? Any guidance would be greatly appreciated.

As far as I know, once you change it to SDF, your clients will not be able to install it from the install bundle page. You will need to deploy the changes to each of your clients which will require SDF enable, tokens set up etc. Have you thought about it? Someone please correct me if I am wrong about this.

Why would they need to enable SDF and do a token setup?

How will you deploy the SDF project?

You're probably thinking there's a smooth path from the deprecated SuiteBundle functionality to the SDF functionality promoted by the deprecation banner on the SuiteBundler. Nope, there isn't. First, if you exported your bundle as an SDF project, be aware that the exporter creates an Account Customization SDF project. There is no uninstall path for an account customization project, so you do not want to use that for 100+ clients. So you will want to create a SuiteApp SDF project and pull your resources into that. There isn't an automatic exporter for that even though it's the closer match to a SuiteBundle. Then, when you try to deploy your SuiteApp SDF project to an account with the existing bundle, every single resource will be treated as a duplication error. The only advice we've gotten from NetSuite is to turn our new SDF project back into a SuiteBundle that can be deployed over the old bundle (in our case the SDF project is a reimplementation with significant overlap of the previous bundle, not just a repackaging).