The Copy to Account Feature allows NetSuite Administrators to copy custom objects from one NetSuite account to another without using any suite bundles.
You can only copy between your own accounts
To run the Copy to Account process you will need an Administrator role
Make sure that the target account has all the prerequisites in place to run this feature
Navigate to Setup -> Company -> Enable Features. Under the Suitecloud subtab, enable the “Suitecloud Development Framework” and “Copy to Account” features and click save.
Next, navigate to Customization -> Lists, Records & Fields -> Record Types and open any existing custom record, or create a new custom record that you want to copy to another account
The Copy to Account option will be visible at the top right corner of the record as shown in the screenshot below
Click the Copy to Account option to send that particular custom record to another account.
Step 1: Select the target account, enter the Deployment Audit Trail Name, and Click Next.
Note: The two accounts should have the same NetSuite Versions.
Step 2: Select the Dependencies and click Next.
Step 3: When the preview is ready, click the Deploy button.
Step 4: After the deployment completes, click Done to complete the process.
The Copy to Account process is now complete
Next, login to the target account and navigate to Customization -> Lists, Records and Fields -> Record Types.
You can view the copied record type in the list.
FAQs on NetSuite Copy to Account
What is the Copy to Account feature in NetSuite?
+
Copy to Account is a built-in administrator tool that lets you copy custom objects - such as custom record types, scripts, workflows, and other SuiteCloud Development Framework (SDF) customizations - from one NetSuite account to another, without packaging them into a SuiteApp bundle. It's commonly used to move customizations between an account's production, sandbox, and development environments.
What do I need before I can use Copy to Account?
+
You need the Administrator role in the source account, and both the SuiteCloud Development Framework and Copy to Account features enabled under Setup → Company → Enable Features → SuiteCloud. The source and target accounts must be on the same NetSuite version, and you can only copy between accounts you have admin access to under your own account family (production, sandbox, and development instances) - not into an unrelated customer's account.
How is Copy to Account different from SuiteBundler or SDF deployment?
+
SuiteBundler packages customizations into a bundle you can install, update, and version across many accounts, which suits ongoing distribution or SuiteApp development. SDF (via command line or an IDE) gives developers full control over deploying and version-controlling customizations as project files. Copy to Account sits between the two: it's a point-and-click way to move a single custom object between your own accounts without building a bundle or setting up an SDF project, which makes it the fastest option for a one-off or occasional transfer.
What can't I copy with Copy to Account?
+
Copy to Account only supports objects that SDF itself supports, and even then it excludes objects that are locked, hidden, or already part of another installed SuiteApp, as well as Single Page Application (SPA) objects. It also doesn't carry over field-label translations on custom forms - if translations matter, use SDF directly instead.
Can I copy more than one custom record at a time?
+
No. Copy to Account moves one custom object at a time - there's no batch or bulk option. If you're migrating a large number of customizations, budget time accordingly or consider SuiteBundler for a one-time bulk transfer instead.
What happens if the deployment fails or has dependency errors?
+
NetSuite checks for and displays object dependencies during the preview step, before you deploy. If a dependency is missing or a field can't be copied, the deployment will flag it as an error at that stage rather than partway through, so it's worth reviewing the preview screen carefully before clicking Deploy. Testing in a sandbox account first is the safest way to catch these issues before they reach production.
