Predections?: I'm converting

Bundled

SuiteApp to a

SuiteApp Control Center

SuiteApp. I need to come up with a way to migrate NetSuite Instances with the

Bundled

SuiteApp to the

SuiteApp Control Center

SuiteApp. Assuming that the 'contents' of each app are the same [Code, Record, Fields and all the customids], I'm wondering if I can #1, Install the

SuiteApp Control Center

SuiteApp over top of the currently installed

Bundled

SuiteApp. #2 Then, uninstall the

Bundled

SuiteApp ... thus leaving the NetSuite instance migrated to the new SuiteApp without loss of any data of configuration?

assuming that they are no locks preventing updates, my prediction is that the control center app will update the bundled components

Believe @dmashburn3 went through the conversion some time ago, though not using Control Center; IIRC you have to manually set the App ID on every object. I'm not sure about what happens when the bundle is removed.

So, potentially leaving the old

Bundled

installed, but dormant (delete all deployment records, and set the scripts to inactive) may be an actual path?

Possibly, but maybe @dmashburn3 or others can provide some better insight during the week.

Thanks @erictgrubaugh & @battk! Always valuable insights.

Never actually made the move, but I'd be worried about: 1. When you install the new SuiteApp with the current bundle in place, if IDs are the same, it might end up replicating fields, records, etc. except the new ones from the SuiteApp will have

_2

tagged on them. I've run into this once or twice where a client actually has a custom field with the same name as something we put in our bundle, and it picks it up changes it. 2. If the above does occur, I've even noticed some really peculiar behavior where all of the scripts actually get modified. I'm not sure exactly what scans or how it scans... but all those fields with

_2

actually got modified in the script as well to include the

_2

. Weird right? 3. I make point 2, because if things do fall that way, in theory, you'll have extra scripts, records, etc. At that point you would need some mechanism to move all of the data over from the bundled records to the SuiteApp records. In theory this could work, however you would still need a mechanism to move data, and you would be left some ugly looking

_2

hanging off the end of everything. We never made the transition on account of the amount of data that would require moving. Let me know if you have any luck though. Perhaps they've replaced the behavior of a SuiteApp install so that somehow it can recognize that you can overlay those records accordingly.

It's a shame NetSuite hasn't provided guidance or recommendations in this regard

Yes there desperately needs to be a transition plan from Bundle -> SuiteApp

I asked about it roughly a year ago and was told it was in the plans. I feel like in order to really drive the market place they envision they have to get bundles moved over. Too many products that because they were built native, rely on the records in the bundle, and thus are in this limbo land.

Well, I'm full steam ahead with the

SuiteApp Control Center

version. I'll keep everyone posted

Looking forward to hearing the results! If you can get it to work, might be time to revisit.

Netsuite, not providing guidance on a new product that they are peddling for product development?

Update: I'm working directly with NetSuite on a critical project that is being migrated to SACC. Let it be known that NetSuite is indeed working internally on a migration path.

@darrenhillconsulting have you learned any more about the migration path "in the works"?

I sure did @Seth Duda... they said "Sorry, we're no longer working toward migration of bundles -> SACC"

what!?