You're reading from NetSuite for Consultants, 2e Your comprehensive guide to becoming a successful NetSuite consultant in 2023

Product type Paperback

Published in May 2023

Publisher Packt

ISBN-13 9781837639076

Length 346 pages

Edition 2nd Edition

Tools

NetSuite

Concepts

Enterprise Resource Planning

Author (1):

Peter Ries

View More author details

Table of Contents (28) Chapters

Preface

1. Section I: The NetSuite Ecosystem, including the Main Modules, Platform, and Related Features

2. Introduction to the NetSuite Ecosystem, Platform, and Related Features FREE CHAPTER

3. Selecting and Applying an Implementation Methodology

4. Creating a Project Plan

5. Section II: Understanding the Client’s Organization

6. Documenting the Organization’s Requirements

7. Analyzing the Organization’s Users and Roles

8. Understanding the Organization’s Accounting and Finance

9. Getting to Know the Organization’s Entities and Items

10. Identifying the Organization’s Main Transactions

11. Section III: Implementing an Organization in NetSuite

12. Custom Forms, Records, and Fields

13. Centers and Dashboards

14. Items and Related Lists

15. Customers, Vendors, Contacts, and Other Entities

16. Financial Transactions and Period Closes

17. Procure-to-Pay Transactions

18. Order-to-Cash Transactions

19. Other Transactions and Custom Transactions

20. Analytics, Reports, and Data Exports

21. Section IV: Managing Gaps and Integrations

22. Managing Gaps and Creating Custom Automations

23. Managing Integrations

24. Managing Data Migrations

25. Other Books You May Enjoy

26. Index

Appendix: My Answers to Self-Assessments

Performing imports for data migration 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

Figure 20.1 – 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 legacy system...