Initial Implementation of NetSuite

Users with the Administrator role oversee the initial implementation of the NetSuite application, working with the NetSuite team. Implementation tasks include:

Account Setup

Setup tasks for your NetSuite account are described in the following table.

Task

More Information

Create a login page that shows your company’s branding on the NetSuite account login page.

Displaying Login Fields on Your Web Page

Make sure that your NetSuite account and integrations don't contain data center-specific identifiers.

Best Practices for Cloud Accounts

Decide what customizations your organization needs based on your business.

SuiteCloud Platform Customization

Make sure your global subscription status follows the regulations in the email recipient's jurisdiction. The email opt-in status in the Global Subscription Status field shows if customers can get email messages from your campaigns and email merges.

Subscription Management

Security and Authentication Setup

NetSuite administrators determine how users and client applications access NetSuite.

Task

More Information

Set a strong password policy for users who access your account.

Password Settings That Can Be Modified

Set the right password requirements for your organization.

Password Requirements and Policies in NetSuite

Set up two-factor authentication for users who handle confidential data.

Two-Factor Authentication (2FA)

Set up token-based authentication so client applications can access NetSuite through APIs.

Token-based Authentication (TBA)

Select and set up the right single sign-on option for your organization.

Authentication Overview

Users, Roles, and Permissions Setup

Employees, vendors, partners, and customers might need access to your NetSuite account. Create custom roles for your organization and add the right permissions and restrictions.

Task

More Information

Give employees only the access they need.

NetSuite Access Overview

Don't assign standard roles to users. Customize standard roles and assign them instead.

Create roles for each job function. Assign more than one role if someone has multiple jobs.

Showing Role Permission Differences

Customizing or Creating NetSuite Roles

Think carefully about the permissions for each role and use restrictions when you need more control.

Permissions and Restrictions

Don't use the Full Access role.

Full Access Role (Deprecated)

Assign Core Administration Permissions to roles when needed.

Core Administration Permissions

Don't use the Global Permissions Feature unless you have to. Whenever you can, use permissions and restrictions instead.

Note:

Global permissions apply to every role an employee has.

Using the Global Permissions Feature

Set preferences to tailor NetSuite to each role if needed.

Setting Role-Based Preferences

Assign the Financial History permission to any role that needs access to customer or vendor transactions.

Granting User Access to Transaction History

Make sure you know how the Advanced Employee Permissions feature changes access to employee records.

Before Enabling the Advanced Employee Permissions Feature

Assign each role to yourself and test it. Make sure is has all permissions and access needed for the whole process.

Permissions Documentation

Assign custom roles to users before they start using the account.

Assigning Roles to an Employee

Create user records.

NetSuite Users Overview

Working with Records

Give new users access.

Giving an Employee Access to NetSuite

Giving Customers Access

Make sure users know how to get help.

Tips for Help Center and SuiteAnswers

Getting Help

Remove employees’ NetSuite access right away when they leave.

Employee Termination

System Integrations

To integrate NetSuite with information from other systems, you can use:

CSV Import

Use the Import Assistant for small or medium data imports with CSV files. If you save your import mapping, you can reuse it for future imports and to import CSV data programmatically. For more information, see Data Migrations.

Web Services

Use web services for large or ongoing data migrations, and when you need to migrate record types that CSV import doesn't support.

Use SOAP web services to move large amounts of data in or out of NetSuite. With SuiteTalk SOAP Web Services, you can build your integration in any language you like.

REST web services let you interact with NetSuite through a REST-based interface without coding.

RESTlets

A RESTlet is a SuiteScript that runs when called by an external application or by another SuiteScript. RESTlets are often used by developers who are familiar with SuiteScript.

RESTlets can retrieve, add, or manipulate data from an external source, so NetSuite requires authentication for RESTlets. The RESTful integration supports stateless communication between client and server.

Refer to the following table for more information about the system integration tools.

Tool

More Information

CSV import for small or medium data imports.

CSV Imports Overview

Web services for large or ongoing data migrations.

SuiteTalk SOAP Web Services Platform Overview

Overview of SuiteTalk REST Web Services

RESTlets to create custom logic and share it with external applications over HTTP.

SuiteScript 2.x RESTlet Script Type

Data Migrations

You'll need to move some company information from your other system into NetSuite. Besides system integrations, comma-separated value (CSV) import is the most way to move small or medium data sets from other applications into NetSuite. CSV import saves time and helps prevents errors since you can add or update many records at one time, instead of entering them manually.

Use web services for large or ongoing data migrations and for migrating record types that CSV import doesn't support. For information, see System Integrations.

Review the following tasks and the detailed information available to prepare for migrating your company’s data.

Task

More Information

Clean up your data before importing, and make sure your CSV files match NetSuite file conventions and record types.

Guidelines for CSV Import Files

Save related data in separate CSV files, for example, save employee data in one file. There is one exception to this guideline: import customers, prospects, and leads with contacts.

Importing Entities and Contacts Together

Follow these best practices when performing CSV imports:

  • Start with a test import using a couple of records.

  • Break large jobs into smaller chunks to help things run smoothly. Each import file can have up to 25,000 records.

  • Run imports during off-peak hours.

When importing transactions:

  • Don't import lots of historical transactions – your storage may be limited. For information about how much space you have, contact your account manager.

  • Imported transactions behave like those you create in the user interface. For example, an imported vendor bill with inventory items affects your inventory.

When you import open accounts payable and accounts receivable transactions, make sure the amounts are not duplicated in the account balances you import later.

Transactions Import Type

Customizations

To support your business processes, you may need to add customizations to NetSuite before you go live. After your initial implementation of NetSuite, administrators need to keep providing technical and system support to users. You may need more configuration and integration as your organization's needs change.

Before you customize, identify what is unique about your business and what you need to support your processes. Then check if NetSuite already has that functionality.

Task

More Information

Plan and review before you build customizations to meet user needs. The SuiteCloud platform gives you several tools to adapt NetSuite for your organization:

  • Customize the NetSuite UI and business logic with scripts or point-and-click options .

  • Search and report on NetSuite data.

  • Create custom roles so users only see the tasks and pages they need.

  • Share your customizations with other accounts.

  • Bring information from other systems into your NetSuite accounts.

SuiteCloud Platform Customization

Limit who can add customizations.

Permissions Documentation

Set up naming conventions for your customizations so users can find the right object.

Conventions for Naming Custom Objects

Custom fields:

  • Suggested naming convention: _abbreviation_description.

  • Use the Description field to explain why the field exists, who requested it, and any notes.

  • Enter field level help in the Help field on the Display subtab to instruct users on what to enter.

Custom Fields

Custom forms:

  • Use the standard forms in NetSuite as templates for custom forms that fit your business needs. For example, you may want to reorganize subtabs or rename fields to match your workflow. After you create custom forms, set them as your preferred forms.

  • Specify a custom field as required on a specific custom form only if it's not always required.

Custom Forms

Setting Validation and Defaulting Properties

Custom records:

  • Create and save your custom record first, and then add fields.

  • Test incrementally as you work with custom records and objects.

  • Set permissions only when the record is ready to use.

Custom Records

Build functional tests to check your business processes in NetSuite.

Suggested Test Plan

Sandbox Management

A NetSuite sandbox is a safe, separate test account where you can develop and test new applications and customizations without affecting your production account. Your sandbox has the same configuration, data, and customizations as your production account.

The administrator requests a sandbox refresh when needed to ensure developers are working in an up-to-date account.

Task

More Information

Monitor sandbox and coordinate refreshes from production as required.

Refreshing Sandbox Accounts

Make sure everyone at your company knows about and is ready for the refresh from production before you request it.

NetSuite Sandbox

Refresh your sandbox only when you're ready. A refresh completely replaces the sandbox account with your production data. After your sandbox is refreshed, it can't be restored to its prior state.

Requesting a Refresh

Monitor sandbox expiry dates.

When a Sandbox Account Expires

Set up the Send Email To option on the Email Preferences page for Sandbox and Release Preview so email messages go to the correct addresses.

Setting Preferences for Sandbox Email

Related Topics

General Notices