NetSuite Customer From iPaaS.com Mapping Documentation

An individual (person) customer can be created and updated in NetSuite from an iPaaS.com customer. The integration maps the customer's name, email, category, subsidiary, and a range of optional contact attributes, and through its child collection the customer's billing/shipping address. Organization (company) customers are handled separately by Add/Update NetSuite Customer Company FROM iPaaS.com. Customers transfer on demand from the iPaaS.com Manual Sync page or automatically when outbound customer triggers are enabled.

ID Format

Manual Sync ID Format

Enter the iPaaS.com record ID of the customer on the Manual Sync page.

External ID Format

On a successful transfer, iPaaS.com records the NetSuite customer's internal ID as the external-ID link, so subsequent transfers update the existing customer rather than creating a new one. Before that link exists, the integration also recognizes an already-existing NetSuite customer by email address (see System Caveats).

Deleted Record Support

Outbound delete is supported. The Delete NetSuite Customer FROM iPaaS.com collection removes the matching NetSuite customer when the corresponding customer is deleted in iPaaS.com, driven by the external-ID link (no field mappings). Automatic delete transfers run only when the customer delete trigger is enabled in Outbound Data Flows.

Custom Field Support

Many optional NetSuite attributes are populated from iPaaS.com custom fields named NetSuite … — for example NetSuite Phone, NetSuite Mobile Phone, NetSuite Home Phone, NetSuite Alt Phone, NetSuite Alt Email, NetSuite Title, NetSuite Account Number, NetSuite URL, NetSuite Ship Complete, NetSuite Is Inactive, and the NetSuite Subsidiary override. Add the matching iPaaS.com custom field to pass an attribute through; when the custom field is empty, the attribute is left unset in NetSuite. This is the integration's round-trip convention: the Add/Update NetSuite Customer TO iPaaS.com direction captures these same NetSuite attributes into the identically named custom fields, so values move both ways without loss.

The template also ships example customer custom-field mappings (custentity3, custentity4, populated from the iPaaS.com Country and Currencies custom fields). Each requires creating the custom field in NetSuite (Customization → Lists, Records & Fields) and a matching iPaaS.com custom field before use.

Mapping Collection Status

Status: Enabled (a single Add/Update collection handles both create and update). This collection has no mapping filter — every customer routed to it is processed.
Trigger Events: Create and Update. Automatic transfers fire on the iPaaS.com customer outbound triggers subscribed in Outbound Data Flows; the collection is also available on demand from the Manual Sync page.

Duplicate or Conflicting Mappings

The following collections also operate on customers; which one processes a given record depends on each collection's filter and the record's person/company nature. Review the filters and Add/Update settings before enabling:

Add/Update NetSuite Customer Company FROM iPaaS.com — organization (company) customers.
Add/Update NetSuite Customer TO iPaaS.com — captures customers from NetSuite into iPaaS.com.

Collision handling

The integration does not use iPaaS.com collision handling for this collection; it prevents duplicates through the external-ID link plus the email address matching key. Because email is the matching key, changing or un-mapping it after customers exist can cause incoming customers to stop matching their NetSuite records and create duplicates. Keep the email mapping stable once live and coordinate any change with your implementation partner.

Supported Child Collections

Add/Update NetSuite Customer Address FROM iPaaS.com — the customer's billing/shipping address.

System Caveats

NetSuite Caveats

Subsidiary is required on OneWorld accounts. Subsidiary_Id defaults to the root subsidiary (commonly Parent Company); confirm the default matches your account and override it per customer via the NetSuite Subsidiary custom field.
Last name is required on a person. When the source has no last name, the integration writes N/A.
Category must already exist in NetSuite. Category_Id resolves from the customer's first category; transfer categories first through Add/Update NetSuite Customer Category FROM iPaaS.com.

iPaaS.com Caveats

Email is the customer matching key. The integration recognizes an existing NetSuite customer by email. Keep the email mapping stable once live — see Collision handling.

Integration-Specific Caveats

"NetSuite …" custom-field convention. Optional attributes are carried through iPaaS.com custom fields named "NetSuite X" and round-trip with the TO-iPaaS direction (see Custom Field Support). Add only the custom fields whose attributes you need.

Setup Requirements

Control Fields and Required Configuration

Mapping	Enables	Action	Required?
IsPerson	Person-customer creation	Evaluates to `true` for this collection — routes the record to a NetSuite individual (person) customer. Company customers use the Customer Company collection.	Control — required
Subsidiary_Id	OneWorld subsidiary assignment	Defaults to the root subsidiary. Placeholder — replace: confirm the default (Parent Company) matches your account; override per customer via the NetSuite Subsidiary custom field.	Required on OneWorld
Email	Duplicate matching	Keep the mapping stable once live — it is the customer matching key.	Recommended (matching key)

Custom fields: to carry the optional contact attributes, create the NetSuite … custom fields you need in iPaaS.com (and the example custentity3/custentity4 custom fields in both NetSuite and iPaaS.com) — see Custom Field Support.

Subscription settings: enable the iPaaS.com customer create/update/delete triggers in Outbound Data Flows for automatic transfers; until then, only Manual Sync transfers run.

Authentication

The integration authenticates to NetSuite using the connection configured for the integration; see NetSuite Connections and Settings.

Integration Flow

An iPaaS.com customer transfers — on demand from the Manual Sync page (enter the customer record ID), or automatically when the customer outbound triggers are enabled in Outbound Data Flows.
The integration resolves the NetSuite subsidiary and category, creates or updates the person customer (matching an existing one by external ID, then by email), and transfers the address child.
Optional contact attributes are populated from the NetSuite … custom fields that are present on the iPaaS.com customer.
The NetSuite customer internal ID is stored back on the iPaaS.com customer as its external ID; subsequent transfers update the existing customer.

Mappings

This collection and its address child have no mapping filter — every routed record is processed. Fields marked Control gate behavior; fields with a Placeholder value ship with an example that must be reviewed (see Setup Requirements).

Add/Update NetSuite Customer FROM iPaaS.com

iPaaS.com data type: Customer

Creates or updates an individual (person) customer record in NetSuite from an iPaaS.com customer, populating many optional NetSuite-specific attributes from iPaaS.com custom fields named "NetSuite X" when present.

Mapping Type	Source Field (iPaaS.com)	Destination Field (NetSuite)	Description
Dynamic Formula	`true`	IsPerson	Control — required for person-customer creation. Marks the record as an individual customer (not a company). This collection creates person-type customers; companies are handled by the Customer Company collections.
Dynamic Formula	`LastName ?? "N/A"`	LastName	Required. NetSuite requires a last name on an individual customer; when the source has none, the integration sends `N/A` rather than leaving it blank.
Field	FirstName	FirstName	Recommended. The customer's first name.
Field	EmailAddress	Email	Recommended (matching key). The customer's email and the primary key for recognizing an existing customer. Changing or un-mapping it after customers exist can break matching and create duplicates — keep stable once live.
Field	Company	CompanyName	Optional. The company name associated with the individual customer.
Dynamic Formula	`await GetCategoryIdByCategoryObj(Categories)`	Category_Id	Optional. Sets the NetSuite customer category from the customer's first category. The category must already exist in NetSuite to be matched.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Subsidiary")`	Subsidiary_Id	Required on OneWorld accounts. Sets the NetSuite subsidiary; defaults to the root subsidiary (Parent Company — Placeholder value, confirm/replace). Override per customer via the NetSuite Subsidiary custom field.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Phone")`	Phone	Optional. Populated from the iPaaS.com custom field NetSuite Phone; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Mobile Phone")`	MobilePhone	Optional. Populated from NetSuite Mobile Phone; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Home Phone")`	HomePhone	Optional. Populated from NetSuite Home Phone; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Alt Phone")`	AltPhone	Optional. Populated from NetSuite Alt Phone; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Alt Email")`	AltEmail	Optional. Populated from NetSuite Alt Email; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Title")`	Title	Optional. Populated from NetSuite Title; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Account Number")`	AccountNumber	Optional. Populated from NetSuite Account Number; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite URL")`	Url	Optional. Populated from NetSuite URL; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Ship Complete")`	ShipComplete	Optional. Populated from NetSuite Ship Complete; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Is Inactive")`	IsInactive	Optional. Whether the customer is inactive; populated from NetSuite Is Inactive; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "Country")`	custentity3	Optional. Example custom-field mapping from the iPaaS.com Country custom field; adapt to your NetSuite custom field or remove if unused.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "Currencies")`	custentity4	Optional. Example custom-field mapping from the iPaaS.com Currencies custom field; adapt to your NetSuite custom field or remove if unused.

Add/Update NetSuite Customer Address FROM iPaaS.com

iPaaS.com data type: Customer Address

Creates or updates the customer's address in NetSuite, with several optional attributes populated from iPaaS.com "NetSuite X" custom fields when present.

Mapping Type	Source Field (iPaaS.com)	Destination Field (NetSuite)	Description
Field	Address1	Addr1	Recommended. The first address line.
Field	Address2	Addr2	Optional. The second address line.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Address 3")`	Addr3	Optional. Third address line, populated from NetSuite Address 3; left unset when empty.
Field	City	City	Recommended. The address city.
Field	Region	State	Recommended. The state or region.
Field	PostalCode	Zip	Recommended. The postal/ZIP code.
Field	Country	Country_RefName	Recommended. The country for the address.
Field	IsPrimaryBilling	IsPrimaryBilling	Recommended. Whether this is the customer's primary billing address.
Field	IsPrimaryShipping	IsPrimaryShipping	Recommended. Whether this is the customer's primary shipping address.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Addressee")`	Addressee	Recommended. The name shown on the address; uses the NetSuite Addressee custom field when present, otherwise the customer's name.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Address Attention")`	Attention	Optional. The address attention line, populated from NetSuite Address Attention; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Address Text")`	AddrText	Optional. The full formatted address text, populated from NetSuite Address Text; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Override")`	Override	Optional. NetSuite's address override flag, populated from NetSuite Override; left unset when empty.
Dynamic Formula	`GetCustomFieldValue(CustomFields, "NetSuite Address External Id")`	ExternalId	Optional. An external identifier for the address, populated from NetSuite Address External Id; left unset when empty.
Dynamic Formula	`PhoneNumber (used when at least 7 characters)`	AddrPhone	Optional. The address phone; set only when the source phone has at least seven characters, to avoid storing partial numbers.

Error Handling

Duplicate customers — if the email matching key is changed or stops being populated after customers exist, incoming customers may stop matching their NetSuite records and duplicates can be created. Resolution: keep the email mapping stable; reconcile duplicates in NetSuite.
Category not found — Category_Id resolves only to a category that already exists in NetSuite. Resolution: transfer the category first through Add/Update NetSuite Customer Category FROM iPaaS.com.
Subsidiary rejection (OneWorld) — NetSuite rejects the customer when the subsidiary does not match. Resolution: confirm the subsidiary name (replace the Parent Company default) or set the NetSuite Subsidiary custom field per customer.

Testing & Validation

Test Scenarios

Create a customer. Manually sync an iPaaS.com customer and confirm a NetSuite person customer is created with name, email, subsidiary, and address, and that the internal ID is stored back on the iPaaS.com customer.
Update a customer. Re-sync the same customer after a change and confirm the existing NetSuite customer is updated rather than a duplicate created (matched by email when no external-ID link exists).
Last-name default. Sync a customer with no last name and confirm NetSuite stores N/A.
Custom-field attributes. Populate a NetSuite … custom field (e.g., NetSuite Phone) and confirm the attribute appears on the NetSuite customer; leave it empty and confirm the attribute is unset.
Category. Sync a customer whose category exists in NetSuite and confirm it is applied; confirm a non-existent category is not created.
Address child. Confirm the address transfers with the correct primary billing/shipping flags.

Validation Checklist

The subsidiary default (Parent Company) matches your account or is overridden per customer.
The email mapping is populated and stable (the matching key).
Categories exist in NetSuite before customers reference them.
Only the NetSuite … custom fields you need are added; example custentity3/custentity4 are adapted or removed.

Additional Notes

Round-trip with the TO direction. The NetSuite … custom fields are populated on the Add/Update NetSuite Customer TO iPaaS.com side, so NetSuite-specific attributes captured from NetSuite can be written back without loss.
Organization (company) customers are documented separately under Add/Update NetSuite Customer Company FROM iPaaS.com.
Known limitations affecting customers will be collected in NetSuite Known Limitations as the Customer feature section is added.