Summary

iPaaS.com Customers can be transferred from Syspro customer accounts through Manual Sync or through automatic transfers raised by the Syspro webhook service. Each transfer creates a new iPaaS.com Customer or updates an existing one, carrying the Syspro customer account number, the customer name and the email address. Capturing customers this way establishes the link between the two systems that later allows Syspro invoices to be attached to the right iPaaS.com customer.

ID Format

Manual Sync ID Format

Enter the Syspro customer account number on the iPaaS.com Manual Sync page. This is the value Syspro holds in the customer account's key field.

Example: 000000000000123

External ID Format

After a successful transfer, iPaaS.com saves the Syspro customer account number as the external ID on a dedicated external-ID record. That record is the primary match used to route every subsequent update to the same iPaaS.com customer, rather than creating a duplicate.

The CustomerNumber mapping additionally writes the same value onto the iPaaS.com customer record itself. That serves two purposes: it makes the Syspro account number visible on the iPaaS.com record, and it acts as a fallback match when no external-ID record yet exists — typically on the first sync, or after an external-ID record has been cleared. Remapping CustomerNumber to a different source is supported, but it disables the fallback match for any customer that already existed in iPaaS.com before the first sync.

Deleted Record Support

Outbound delete is not supported for this entity. The integration does not implement a delete operation for customers, delete mappings are not included in the default templates, and deleting a customer account in Syspro will not propagate to iPaaS.com. The iPaaS.com customer record remains in place until it is removed there directly.

Mapping Collection Status

Status: Enabled. The collection carries no mapping filter, so every Syspro customer routed to it is processed.

Trigger Events: customer/created and customer/updated. Both are raised by database triggers installed in the subscriber's own Syspro database and relayed by the Syspro webhook service. Both are enabled by default in the shipped database configuration.

Duplicate or Conflicting Mappings

Add/Update Syspro Customer FROM iPaaS.com operates on the same entity in the opposite direction, writing iPaaS.com customers into Syspro.

Because the two collections move customer data in opposite directions, subscribers or their MiSP should decide which system is the source of truth for customer records before enabling both, and review each collection's filters and Add/Update settings accordingly. Running both without that decision can cause values to be overwritten in each direction in turn — a name edited in iPaaS.com is pushed to Syspro, then captured back unchanged, and vice versa.

Duplicate customers are prevented by the external-ID link rather than by a configurable conflict-resolution setting. This entity does not support collision handling, so there are no selectable collision methods on this collection.

Supported Child Collections

None. This collection has no child collections — Syspro customer addresses and contacts are not captured.

System Caveats

Syspro Caveats

Syspro holds a single customer name. There are no separate company and personal name fields, so the value captured into the iPaaS.com Company field may be either a business name or a person's name depending on the account.
Names arrive upper-cased for round-tripped customers. A customer originally created in Syspro by the outbound collection carries an upper-cased name, because that transfer converts it before writing. Customers created directly in Syspro carry whatever casing was entered there.
Email address is mandatory in Syspro. A customer account that exists in Syspro will normally have one to send.

iPaaS.com Caveats

Customer number and email address are both required. iPaaS.com rejects a customer record missing either. A legacy Syspro account with no email address on file cannot be captured; the transfer fails and the error appears under Dashboard / Integration Monitoring / Error Logs.
Company is not required but is strongly recommended — without it the customer appears in iPaaS.com with no business name, which makes it harder to identify in lists and reports.

Setup Requirements

Syspro Configuration

Automatic transfers depend on components installed in the subscriber's own environment:

Install the Syspro database objects that raise customer change events.
Confirm that the customer event subscriptions are recorded and enabled in the Syspro database. Both customer events are enabled in the shipped configuration.
Install and run the Syspro webhook service on a Windows server that can reach both the Syspro database and iPaaS.com.

Refer to the Syspro Installation Instructions for the full procedure. No configuration is required on the iPaaS.com side to receive these events.

iPaaS.com Configuration

No subscriber-facing setup is required beyond an authenticated subscription. Manual Sync is available immediately.

Integration Flow

A customer is created or changed in Syspro, or a subscriber initiates a Manual Sync using the Syspro customer account number.
For automatic transfers, the change raises a customer/created or customer/updated event, which the Syspro webhook service relays to iPaaS.com. For Manual Sync, the transfer begins directly.
The integration retrieves the customer record from Syspro.
iPaaS.com looks for an existing external-ID record matching the Syspro customer account number. If one is found, the transfer updates the linked iPaaS.com customer. If none is found, iPaaS.com falls back to matching an existing customer whose CustomerNumber equals the Syspro account number, and links it.
If neither match succeeds, a new iPaaS.com Customer is created.
The customer number, email address and name are written.
The external-ID record is saved so subsequent transfers route to the same customer.

Mappings

Add/Update Syspro Customer TO iPaaS.com

iPaaS.com data type: Customer

This collection captures the Syspro customer account into iPaaS.com. It carries no mapping filter, so every customer routed to it is processed.

Mapping Type	Source Field (Syspro)	Destination Field (iPaaS.com)	Description
Field	`Customer`	CustomerNumber	Required. The Syspro customer account number. iPaaS.com rejects a customer record without one. Also acts as the fallback match key when no external-ID record yet exists.
Field	`Email`	EmailAddress	Required. The customer email address. iPaaS.com rejects a customer record without one. A legacy Syspro record with an empty address fails to transfer.
Field	`Name`	Company	Recommended. The Syspro customer name. Syspro holds a single name field, so this may be a business name or a person's name. Arrives upper-cased for customers created by the outbound transfer.

Error Handling

Errors raised by this collection are catalogued in the Syspro Error Messages article, which is the companion reference for the integration's error text and resolutions. The two failure modes specific to this collection are a Syspro account with no email address and one with no customer number; both are rejected by iPaaS.com and appear under Dashboard / Integration Monitoring / Error Logs with the field named.

Testing & Validation

Test Scenarios

Create a new customer account in Syspro with a customer number, name and email address, and verify it appears in iPaaS.com with all three values populated.
Update the name on an existing Syspro customer and verify the change propagates to the iPaaS.com Company field without creating a duplicate customer.
Attempt a transfer for a Syspro account with no email address and confirm the transfer fails with an error naming the missing field.
Perform a Manual Sync using the documented ID format and confirm the correct customer is retrieved and transferred.
Transfer the same customer twice and confirm the second transfer updates the existing iPaaS.com record rather than creating a second one, confirming the external-ID link is working.
Stop the Syspro webhook service, change a customer in Syspro, and confirm no transfer occurs; restart the service and confirm the change is then relayed.

Validation Checklist

The Syspro customer account number appears in the iPaaS.com CustomerNumber field.
The email address matches the Syspro account.
The customer name appears in the Company field.
Repeat transfers update rather than duplicate.
Customer events are recorded and enabled in the Syspro database.
The Syspro webhook service is running and can reach iPaaS.com.

Additional Notes

Customer addresses and contacts are out of scope. Syspro customer addresses are not captured by this collection.
Credit and financial data is out of scope. Credit limits, terms codes, balances and price codes are not captured.
Bulk initialization is not supported. An existing Syspro customer base cannot be loaded in one operation. Subscribers or their MiSP should use bulk sync using Postman to load customers in volume.

Syspro to iPaaS.com Customer Mapping Documentation