Book Image

NetSuite for Consultants

By : Peter Ries
Book Image

NetSuite for Consultants

By: Peter Ries

Overview of this book

NetSuite For Consultants takes a hands-on approach to help ERP and CRM consultants implement NetSuite quickly and efficiently, as well deepen their understanding of its implementation methodology. During the course of this book, you’ll get a clear picture of what NetSuite is, how it works, and how accounts, support, and updates work within its ecosystem. Understanding what a business needs is a critical first step toward completing any software product implementation, so you'll learn how to write business requirements by learning about the various departments, roles, and processes in the client's organization. Once you've developed a solid understanding of NetSuite and your client, you’ll be able to apply your knowledge to configure accounts and test everything with the users. You’ll also learn how to manage both functional and technical issues that arise post-implementation and handle them like a professional. By the end of this book, you'll have gained the necessary skills and knowledge to implement NetSuite for businesses and get things up and running in the shortest possible time.
Table of Contents (27 chapters)
1
Section 1: The NetSuite Ecosystem, including the Main Modules, Platform, and Related Features
5
Section 2: Understanding the Organization You Will Implement the Solution for
11
Section 3: Implementing an Organization in NetSuite
21
Section 4: Managing Gaps and Integrations
Appendix: My Answers to Self-Assessments

Performing imports for testing and other reasons

Once you start to collect a set of files from another system, you want to bring them in, in a limited fashion, to test the waters for the migration. The first step in this process is typically helping the client know what NetSuite is looking for, with each of the lists and record types they want to import. The NetSuite services team typically provides templates, in a set of Excel files, to show the client which columns are to be included with each import, which of those are required or optional, and what the data type for each field should be.

The following table shows what they usually look like, including extra rows explaining how the data should be formatted, and so on:

Figure 20.1 – An example of a CSV template for an entity record

Sending a client a set of templates and guiding them in their use is typically enough to get them started. They will determine which columns in the data files from their...