CRITICAL ALERT FOR CUSTOMERS RUNNING BOX FOR ORACLE NETSUITE V0.1.0 -- you are at risk of losing critical bundle data and we urge you to file a ticket with Box Product Support for upgrade assistance. THIS ALERT APPLIES ONLY TO CUSTOMERS RUNNING BOX FOR ORACLE NETSUITE V0.1.0. If you are running any other version, you can upgrade safely at any time. Please see this technical bulletin for further details.
A video walkthrough of the end-to-end process w/ commentary is available here.
With the new and improved v2 Box for Oracle NetSuite integration, administrators gain more control; they can configure and enforce role-based permissions on a more granular basis. And everyone has a more streamlined and intuitive experience thanks to more logically-organized folders and precise mapping to corresponding NetSuite records – especially as the revised folder naming convention matches the NetSuite record name.
The primary difference between the earlier Box for Oracle NetSuite integration and v2 is the default folder structure. In the previous version of the integration, all NetSuite record types and associated files were located in one flat level, beneath one NetSuite root folder. The v2 integration provides a nested file structure; each NetSuite record type has its own parent folder, located within a new NetSuite root folder for each NetSuite instance you associate with your Box account. Within each NetSuite record type parent folder, people can create sub-folders for storing all documents and files related to a specific record of that type – for example, all of the invoices and receipts relevant to a specific journal entry. By contrast, the earlier version of the Box for Oracle NetSuite integration limited you to a flatter folder structure that could quickly become difficult to scan for a particular NetSuite record folder.
Installing the new integration establishes a new root folder with this nested structure:

Setting up a Migration Path from v1 to v2
After you install the Box for Oracle NetSuite bundle, you can set up the migration path for existing v1 folders into the new v2 folder structure. To enable the migration, you must first connect the folders and establish the v2 service account user (such as AutomationUser_613333_xxx@boxdevedition.com ) as a co-owner of your v1 root folder (pictured here). Click the "More Options" button, then share. Add the user as a co-owner and select Send. Your root folder name may be different than the example.

Important: If you are updating your installation from v1 to v2, continue with the procedure below. If you are installing a Box for Oracle NetSuite bundle for the first time, you can skip the rest of this process and begin configuring the integration.
If you are migrating from v1 to v2 and have enabled the setting labeled Prevent users from accessing NetSuite content from their Box account for your Box Enterprise/Business settings in Admin Console > Apps > Individual Application Controls > "Netsuite" > Configure, this prevents content from migrating to the V2 folder structure. Instead, the system prompts you to select a folder or create a new default blank folder under the Box Content tab. To ensure content migrates to the V2 folder structure, you must disable this setting after you install NetSuite v2.
Regarding the availability of "Prevent users from accessing NetSuite content from their Box account": This setting is only visible to the Box user who first created the connection between the Box Files integration in NetSuite and Box. If you don't see this setting and you are not able to access the files you're collaborating on in NetSuite directly from your Box account when logged into https://account.box.com, please contact Box Support.
Connecting your v1 and v2 folders
The Box for NetSuite v2 root folder is owned by a system-generated account called a service account. For the passive migration to occur, you must add this service account's email address as a co-owner on your v1 root folder.
Note: The procedure below applies only to Business+ and higher Box accounts. If yours is a Business account or lower, please contact support.
To locate this email address:
- In the Admin Console's left menu, click Content. Box displays the Content Manager page.
- In the left pane, click Users and locate the account name Box-for-Netsuite.
- Right-click Box-for-Netsuite, then select Login into user's account. Box logs you in as AutomationUser.
- In the top-right corner of the account window, click the account icon and select Account Settings.
- In the Account tab, scroll down to the Login and Email Addresses section. The email address is under Default Email Address, and is in the format AutomationUser_613333_xxx@boxdevedition.com (the "xxx" represents the last alphanumeric string, which varies by Box EID. Below is an example.)

Configuring your Migration Settings
During installation, admins can opt to enable migration of existing Box folders to the new v2 root folder. But enabling the migration does NOT automatically move ALL existing Box folders; this is not a mass migration tool. Rather, Box uses a “passive migration” method. This means that folders associated with a pre-existing NetSuite record do not move until one of your users accesses them. When someone does access one of these folders, only then does Box automatically move that folder from the old, flatter v1 root folder to your new NetSuite nested root folder, under the corresponding record type parent folder. This “passive migration” essentially means that, over time, your original root folder ultimately becomes an archive folder; as people access active files and folders during the course of their jobs, those files and folders move out and reorganize into the new nested structure.
This also means, with the installation of the new Box for Oracle NetSuite bundle, admins have two root folders – a v1 and a v2. Examine both Move v1 Content to v2 and Upgraded from v1 periodically. Over time you will see only the v2 root folder contains active folders and files.
To begin enabling the migration, in NetSuite, click Customization > List, Record, and Fields > Record Types to display the Record Types screen.

The screen now displays a table listing all the record types the integration recognizes by default. Click List.

The Box Integration Config record displays. Click Edit.

A new Box Intgration Config screen displays.
Enter your configuration details in this screen. The table below describes how your displays differ, depending on which boxes you have checked in this screen (above) -- that is, which integration(s) you have implemented.
Only “upgraded from v1” is checked. |
- If a folder existed for this record in v1 (that is, in the Box Files tab), it automatically displays in the v2 Box Content tab for the record. But the folder itself remains in the v1 structure.
- If a folder did not exist for this record in v1, the system prompts you to select choose folder or default.
- If you select choose folder, the folder you selected remains where it is in your folder tree.
- If you select default, the system creates a new folder in the v2 structure.
|
Only “move v1 content to v2” is checked. |
This is equivalent to having neither “upgraded from v1” or “move v1 content to v2” checked. Refer to the last row, below. |
Both “upgraded from v1” and “move v1 content to v2” are checked. |
Your folders remain in the v1 folder structure until someone accesses the record. Then the folder automatically moves to the v2 folder structure. |
Neither “upgraded from v1” or “move v1 content to v2” are checked. |
The system prompts you to select choose folder or default upon visiting a record.
- If you select choose folder, the folder you selected remains where it is in your folder tree.
- If you select default, the system creates a new folder in the v2 structure.
Note Your v1 folder structure is not recognized in the v2 Box Content tab. However, your v1 folder structure continues to display in the v1 Box Files tab if v1 is still installed.
|
Note: If you install the Box for Oracle NetSuite integration and you choose not to migrate existing Box folders into the new v2 nested folder hierarchy, all pre-existing content folders remain in their original flat hierarchy and do not migrate. Only new folders, created after the integration is installed and enabled, populate the new structure. As a result, people may need to search for specific documents inside of two root folders, rather than one.
Known Limitations
Due to technical limitations of the NetSuite Lead-to-Customer conversion process, the following record types do not passively migrate:
- Prospect records
- Customer records
Unfortunately, you must manually migrate the associated Box folders of these records from the v1 to v2 folder structure.
You can manually migrate Customer and Prospect records either by starting in NetSuite or by starting in Box.
To migrate starting in NetSuite:
- In NetSuite, go to the desired NetSuite record you want to migrate.
- Go to the Box content sub-tab and click Default. This creates a new Box folder for this record in the v2 folder structure.
- In Box, locate the previously associated v1 folder and move its contents into the v2 folder that you created in Step 2, above.
Detailed steps on how to install the Box for Oracle NetSuite bundle.
Detailed steps on how to set up and enable the Box for Oracle NetSuite integration.
tech_writers_swarm_kb