1. Switching Everything to a Child Subsidiary
• For New Transactions:
• If your goal is for future transactions to default to a specific child subsidiary (instead of the default parent), you can adjust your transaction forms, preferences, or workflows so that the child subsidiary is selected by default. This means that going forward, new records will be created under that child subsidiary.
• For Existing Data:
• Changing the subsidiary on historical or posted transactions is generally not supported. Once a transaction is posted or a record is saved with a subsidiary, the subsidiary field is often locked for data integrity reasons. Reassigning existing data to a different subsidiary typically isn’t feasible without a significant data migration effort, and even then, it may not be supported by NetSuite.
• Considerations:
• If your company’s structure or reporting needs have changed, it might be better to handle the change going forward rather than attempting to “move” existing records. For new transactions, you can set the desired child subsidiary as the default. If historical data needs to be reported differently, consider using saved searches or reporting tools that filter or group data by the desired subsidiary.
2. Multiple Parent Subsidiaries
• Single Top-Level Parent:
• NetSuite OneWorld is designed to have one top-level parent subsidiary. All other subsidiaries must be created as children (or further descendants) under that parent. You cannot have multiple top-level (or “parent”) subsidiaries within a single account.
• Hierarchy Flexibility:
• While you cannot create multiple independent parent subsidiaries, you can build a multi-tiered hierarchy. For example, you can have a parent subsidiary with multiple direct child subsidiaries. If needed, one of those child subsidiaries can itself have further child subsidiaries. However, the entire structure will always reside under the single, original top-level parent.
Summary
• Switching Transaction Defaults:
• You can change defaults for new transactions to use a child subsidiary. This can be achieved by customizing forms, setting preferences, or using workflows/scripts.
• Historical Records:
• Changing the subsidiary on existing (especially posted) transactions is not generally supported.
• Multiple Parents:
• NetSuite does not allow multiple top-level parent subsidiaries. All subsidiaries must be part of one hierarchy with a single parent at the top.
If your organization’s business processes have changed and you need a different organizational structure, it might be worthwhile to consult with NetSuite Support or a professional consultant who can review your account’s configuration and suggest the best approach for your specific situation.