NetSuite Customer To iPaaS.com Mapping Documentation

An individual (person) customer can be captured from NetSuite into iPaaS.com. The integration records the customer number, name, email, categories, and a range of NetSuite-specific attributes, and through its child collections the customer's address and parent relationship — producing an iPaaS.com customer that mirrors the NetSuite customer. Organization (company) customers are captured separately by Add/Update NetSuite Customer Company TO iPaaS.com. Customers transfer on demand from the Manual Sync page or automatically on NetSuite customer events.

ID Format

Manual Sync ID Format

Enter the NetSuite customer's internal ID on the Manual Sync page.

External ID Format

iPaaS.com records the NetSuite internal ID as the external-ID link (the primary match for subsequent updates). The NetSuite internal ID is also captured into the iPaaS.com Customer Number, which gives visibility on the iPaaS.com customer and serves as a fallback match key when no external-ID record yet exists.

Deleted Record Support

Inbound delete is supported: the Delete NetSuite Customer TO iPaaS.com collection removes the linked iPaaS.com customer when the customer is deleted in NetSuite (driven by the external-ID link). It runs only when the corresponding NetSuite delete event is enabled and the NetSuite-side webhook scripts are installed.

Custom Field Support

A range of NetSuite-specific attributes — phone, mobile/home/alternate phone, alternate email, title, account number, URL, ship-complete, inactive flag, and subsidiary — are captured into iPaaS.com custom fields named NetSuite … (for example NetSuite Phone, NetSuite Subsidiary). These are the capture side of the integration's round-trip convention: the same custom fields are read back on the Add/Update NetSuite Customer FROM iPaaS.com side, so a customer can round-trip without losing its NetSuite-specific attributes. Add the matching iPaaS.com custom fields to retain these attributes.

Mapping Collection Status

Status: Enabled (a single Add/Update collection handles both create and update).
Trigger Events: customer/created, customer/updated. Enable inbound transfers in Inbound Data Flows and install the NetSuite-side webhook scripts (see NetSuite Connections and Settings). Whether an event creates or updates the iPaaS.com customer depends on the external-ID link, not the event name. Manual Sync is always available.

Duplicate or Conflicting Mappings

Add/Update NetSuite Customer Company TO iPaaS.com — organization (company) customers.
Add/Update NetSuite Customer FROM iPaaS.com — writes customers to NetSuite (the reverse direction).

Collision handling

Matching uses the external-ID link (primary) and the captured Customer Number (the NetSuite internal id) as the fallback key. No iPaaS.com collision-handling method is configured for this collection.

Supported Child Collections

Add/Update NetSuite Customer Address TO iPaaS.com — the customer's address.
Add/Update NetSuite Customer Relationship TO iPaaS.com — the customer's parent relationship.

System Caveats

NetSuite Caveats

Subsidiary filter. Only customers in the subsidiary named in the filter are captured (see Mappings). The shipped name is a placeholder.

iPaaS.com Caveats

Email and Customer Number. The iPaaS.com API requires a customer email; the captured Customer Number (NetSuite internal id) is the fallback match key. Keep both populated.

Integration-Specific Caveats

"NetSuite …" round-trip convention. NetSuite-specific attributes are captured into the identically named custom fields read back by the FROM direction (see Custom Field Support).
Parent company is created for you. If the customer belongs to a parent company or customer not yet in iPaaS.com, the integration creates that parent automatically as a prerequisite during capture (a failure blocks the customer) — you do not pre-create it.
Customer pricing becomes iPaaS.com categories. A NetSuite customer's pricing group and/or price level — the things that set the prices that customer sees — are captured as iPaaS.com customer categories. The Customer Pricing Source setting, in the NetSuite subscription's Subscription Settings in iPaaS.com, controls which is used: PRICE_GROUP_ONLY (the default — pricing group only), PRICE_LEVEL_ONLY (price level only, with an optional Default Price Level fallback), GROUP_THEN_LEVEL (pricing group, else price level), or LEVEL_THEN_GROUP (price level, else pricing group). You do not need to pre-create these categories — the integration creates the matching iPaaS.com customer category automatically as a prerequisite during capture; they can also be bulk-loaded via Add/Update NetSuite Customer Pricing Group TO iPaaS.com.

Setup Requirements

Control Fields and Required Configuration

Subsidiary filter — placeholder. The capture filter is hardcoded to the subsidiary named Parent Company; replace it with your subsidiary (or broaden it) so the customers you intend to capture are not silently excluded.
Customer Pricing Source (and the optional Default Price Level fallback) — found in the NetSuite subscription's Subscription Settings in iPaaS.com. Controls whether a customer's NetSuite pricing group, price level, or one-then-the-other becomes the iPaaS.com categories (PRICE_GROUP_ONLY default, PRICE_LEVEL_ONLY, GROUP_THEN_LEVEL, LEVEL_THEN_GROUP).
NetSuite … custom fields — create the iPaaS.com custom fields you want to retain (the capture side of the round-trip).
Inbound Data Flows + webhook scripts — enable the NetSuite customer events and install the NetSuite-side webhook scripts (see NetSuite Connections and Settings) for automatic capture.

Authentication

The integration authenticates to NetSuite using the connection configured for the integration; the webhook scripts that emit NetSuite events are documented in NetSuite Connections and Settings.

Integration Flow

A NetSuite customer is captured — on demand from the Manual Sync page (enter the NetSuite internal ID), or automatically on customer/created / customer/updated events when Inbound Data Flows and the webhook scripts are in place.
The subsidiary filter admits only customers in the configured subsidiary.
The integration creates or updates the iPaaS.com customer (matched by external ID, then by Customer Number), capturing the NetSuite-specific attributes into the NetSuite … custom fields, and transfers the address and relationship children.

Mappings

The address and relationship children have no filter. Fields marked Control gate behavior; the subsidiary value in the parent filter is a placeholder to replace.

Add/Update NetSuite Customer TO iPaaS.com

iPaaS.com data type: Customer

Mapping Filter

var subsidiaryId = await GetSubsidiaryIdByName("Parent Company");
if(subsidiaryId != null && Subsidiary_Id != null && Subsidiary_Id == subsidiaryId)
    return true;
else
    return false;

Filter Description. Resolves the internal ID of a named subsidiary, then captures the customer only when the customer's subsidiary matches that ID; customers in any other subsidiary (or with no subsidiary) are skipped. Placeholder value — replace during implementation: Parent Company is an example subsidiary name — only customers in this one subsidiary are captured; change it to your subsidiary (or broaden the filter if you capture from more than one).

Captures a NetSuite customer into iPaaS.com, with NetSuite-specific attributes stored in iPaaS.com "NetSuite …" custom fields.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Field	Id	CustomerNumber	Required. The NetSuite customer's internal ID, captured as the iPaaS.com customer number — links the customer back to NetSuite and serves as the fallback match key.
Field	Email	EmailAddress	Required. The customer's email; the iPaaS.com API requires it, and it is the key used to match customers between systems.
Dynamic Formula	`if(IsPerson){ return FirstName; } else { ...name part from company name }`	FirstName	Recommended. The first name — the NetSuite first name for person customers; for companies, a name part derived from the company name.
Dynamic Formula	`if(IsPerson){ return LastName; } else { ...name part from company name }`	LastName	Recommended. The last name, derived as above.
Field	CompanyName	Company	Optional. The company name captured from NetSuite.
Dynamic Formula	`await ConvertNetSuiteCategoryToiPaaS(Category, GroupPricing, PriceLevel, false)`	Categories	Optional. Converts the NetSuite category, and optionally pricing group / price level, into iPaaS.com categories per the Customer Pricing Source setting.
Field	Comments	Comment	Optional. Free-text comments captured from the NetSuite customer.
Field	AccountNumber	NetSuite Account Number	Optional. Captures the NetSuite account number into the iPaaS.com NetSuite Account Number custom field.
Field	Phone	NetSuite Phone	Optional. Captures the NetSuite phone into the NetSuite Phone custom field.
Field	MobilePhone	NetSuite Mobile Phone	Optional. Captures the NetSuite mobile phone into the NetSuite Mobile Phone custom field.
Field	HomePhone	NetSuite Home Phone	Optional. Captures the NetSuite home phone into the NetSuite Home Phone custom field.
Field	AltPhone	NetSuite Alt Phone	Optional. Captures the alternate phone into the NetSuite Alt Phone custom field.
Field	AltEmail	NetSuite Alt Email	Optional. Captures the alternate email into the NetSuite Alt Email custom field.
Field	Title	NetSuite Title	Optional. Captures the title into the NetSuite Title custom field.
Field	Url	NetSuite URL	Optional. Captures the website URL into the NetSuite URL custom field.
Field	ShipComplete	NetSuite Ship Complete	Optional. Captures the "ship complete" preference into the NetSuite Ship Complete custom field.
Field	IsInactive	NetSuite Is Inactive	Optional. Captures whether the customer is inactive into the NetSuite Is Inactive custom field.
Field	Subsidiary_Id	NetSuite Subsidiary	Optional. Captures the NetSuite subsidiary into the NetSuite Subsidiary custom field; the FROM direction reads this same field to assign a subsidiary, so a round-tripped customer keeps its subsidiary.

Add/Update NetSuite Customer Address TO iPaaS.com

iPaaS.com data type: Customer Address

Captures the NetSuite customer's address into iPaaS.com, with NetSuite-specific attributes stored in "NetSuite …" custom fields.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Field	Addr1	Address1	Recommended. The first address line captured from NetSuite.
Field	Addr2	Address2	Optional. The second address line.
Field	City	City	Recommended. The city.
Field	State	Region	Recommended. The state/region.
Field	Country_RefName	Country	Recommended. The country.
Field	Zip	PostalCode	Recommended. The postal/ZIP code.
Field	IsPrimaryBilling	IsPrimaryBilling	Recommended. Whether this is the primary billing address.
Field	IsPrimaryShipping	IsPrimaryShipping	Recommended. Whether this is the primary shipping address.
Field	AddrPhone	PhoneNumber	Optional. The address phone number.
Static	`true`	PreventDuplicate	Control. Tells iPaaS.com to avoid creating a duplicate address row on repeated syncs; keep `true`.
Dynamic Formula	`if (Addressee != null){ ...first name from Addressee }`	FirstName	Recommended. The recipient first name, extracted from the NetSuite address addressee.
Dynamic Formula	`if (Addressee != null){ ...last name from Addressee }`	LastName	Recommended. The recipient last name, extracted from the addressee.
Dynamic Formula	`Parent.CompanyName`	Company	Optional. The company name on the address, from the parent customer.
Field	Addressee	NetSuite Addressee	Optional. Captures the addressee into the NetSuite Addressee custom field.
Field	Attention	NetSuite Address Attention	Optional. Captures the attention line into the NetSuite Address Attention custom field.
Field	AddrText	NetSuite Address Text	Optional. Captures the full formatted address text into the NetSuite Address Text custom field.
Field	ExternalId	NetSuite Address ExternalId	Optional. Captures the address external ID into the NetSuite Address ExternalId custom field.
Field	Addr3	NetSuite Address 3	Optional. Captures the third address line into the NetSuite Address 3 custom field.
Field	Override	NetSuite Override	Optional. Captures the address override flag into the NetSuite Override custom field.

Add/Update NetSuite Customer Relationship TO iPaaS.com

iPaaS.com data type: Customer Relationship

Captures a NetSuite customer's parent relationship (the customer or company it is related to) into iPaaS.com.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`var customerId = await GetSpaceportIdAsync(Id.Split("\|")[0]...)`	RelatedToId	Required. Identifies the related parent customer or company in iPaaS.com, resolved from the related NetSuite record; the related record must already exist in iPaaS.com to be linked.
Dynamic Formula	`IsPerson ? "Parent Customer" : "Parent Company"`	Type	Recommended. The relationship type — Parent Customer when the related record is an individual, Parent Company when it is a company.
Static	`true`	IsPrimary	Control. Marks this as the primary relationship.

Error Handling

Customer skipped by the subsidiary filter — a customer in a non-matching subsidiary is silently skipped (not an error). Resolution: if expected customers are missing, update the subsidiary in the filter.
Relationship not linked — RelatedToId resolves only to a parent customer/company that already exists in iPaaS.com. Resolution: ensure the related record has been captured first.

Testing & Validation

Test Scenarios

Capture a customer. Manually sync a NetSuite customer (in the configured subsidiary) and confirm the iPaaS.com customer is created with name, email, Customer Number, and the NetSuite … attributes.
Update. Re-sync and confirm the existing iPaaS.com customer is updated (matched by external ID / Customer Number).
Subsidiary filter. Sync a customer in a different subsidiary and confirm it is skipped; update the filter and confirm it is then captured.
Address + relationship. Confirm the address and parent relationship children transfer.
Round-trip. Confirm the NetSuite … custom fields are populated so a subsequent FROM-iPaaS sync retains them.

Validation Checklist

The subsidiary filter names your subsidiary (not the Parent Company placeholder).
The Customer Pricing Source setting is configured for how categories should resolve.
The NetSuite … custom fields exist in iPaaS.com to retain the attributes.
Inbound Data Flows and the NetSuite webhook scripts are in place for automatic capture.

Additional Notes

Round-trip with the FROM direction. The NetSuite … custom fields populated here are read back by Add/Update NetSuite Customer FROM iPaaS.com.
Organization (company) customers are documented separately under Add/Update NetSuite Customer Company TO iPaaS.com.
Known limitations affecting customers will be collected in NetSuite Known Limitations.