Understanding the Default NetSuite Schema

When you connect your NetSuite account to RevOS, we automatically sync a core set of standard NetSuite records and relationships. This enables you to explore your ERP and CRM data with full relational context — no manual modeling required.

Default Synced NetSuite Records

The following NetSuite record types are synced by default:

Customers

Contacts

Sales Orders

Opportunities

Opportunity Line Items

These objects reflect the most frequently used components of the standard NetSuite schema for managing customers, transactions, and sales processes.

💡

Additional NetSuite objects (e.g., Items, Employees, Transactions, Custom Records) can be enabled on request to fit your specific business processes.

How Records Are Connected

RevOS builds a semantic model that mirrors the logical structure of NetSuite data. This includes key relationships between entities such as customers, contacts, and transactions.

Here’s an overview of the relationships between core NetSuite records:

Relationship Types

1 : N – one-to-many relationship

N : 1 – many-to-one relationship

Contacts

Related to a Customer via the company field (N:1)

Multiple contacts can belong to the same customer

Example: A business customer may have several employee contacts

Customers

Central object in the model — linked to:

Multiple Contacts

Multiple Sales Orders

Multiple Opportunities

Customers represent organizations or individuals involved in transactions

Sales Orders

Linked to a Customer via the entity field (N:1)

Represents a committed transaction (e.g., a sale)

A customer can have multiple sales orders over time

Opportunities

Linked to a Customer via the entity field (N:1)

Represents a potential revenue opportunity (e.g., a sales lead)

Can include multiple Opportunity Items

Opportunity Line Items

Linked to an Opportunity via opportunity.id (N:1)

Represent individual products or services being considered in a deal

Unnested from the JSON item.items array in the opportunity record

Need More Data?

If your team uses additional NetSuite records — such as Items, Transactions, Employees, or custom fields and records — just let us know. We’ll help you extend your semantic model to fully support your ERP analytics and reporting needs.

Oracle NetSuite Semantic Model