Which direction does data flow between SAP Business One and Zoho CRM?

Business partners, contacts, and items from SAP Business One flow primarily into Zoho CRM as Accounts and Contacts. Sales orders from SAP are matched to Zoho deals for unified pipeline visibility. Zoho deals and quotes are read back to match against SAP sales orders and invoices, closing the opportunity-to-cash loop. The integration is bidirectional for reference data alignment and unidirectional for transactional records.

Does ml-connector handle SAP Business One session tokens and Zoho OAuth refresh automatically?

Yes. ml-connector logs into SAP Business One once, reuses the B1SESSION cookie across requests, and refreshes before the 30-minute inactivity timeout. For Zoho CRM, it stores the refresh token encrypted, automatically refreshes the access token when calls return 401, and renews webhook notification channels before they expire every 24 hours.

What happens if SAP Business One is on-premise with a self-signed certificate?

ml-connector accepts self-signed TLS certificates on SAP Business One Service Layer via customer configuration and does not require a public CA certificate. You provide the full endpoint URL including port, and ml-connector validates it on first connection. Webhook Messenger Service activation on the SAP server is optional; polling with OData filters is the recommended default.

SAP Business OneZoho CRM

SAP Business One and Zoho CRM integration

SAP Business One runs your financials, inventory, and purchasing. Zoho CRM manages your sales pipeline and customer relationships. Connecting the two keeps your customer master and sales activity aligned across both systems. New business partners and items created in SAP automatically appear in Zoho, and deals closed in Zoho can be matched back to SAP sales orders and invoices for seamless order-to-cash visibility.

How SAP Business One works

SAP Business One exposes business partners, invoices, purchase invoices, purchase orders, incoming payments, outgoing payments, journal entries, chart of accounts, dimensions, profit centers, and items through OData v4 REST at a customer-specific Service Layer endpoint. Authentication uses a session token obtained via POST /Login, which returns a B1SESSION cookie valid for 30 minutes of inactivity and must be refreshed before timeout. OAuth 2.0 and OIDC are available in SAP Business One v10.0 FP 2305 and later if the customer has IAM configured. SAP Business One also supports webhooks for Create/Update/Delete events in v10.0 FP 2602 and later if the Webhook Messenger Service is activated server-side, but polling with UpdateDate filters is the recommended default since webhooks require SAP administrator setup and may not be enabled in all deployments.

How Zoho CRM works

Zoho CRM exposes accounts, contacts, vendors, invoices, purchase orders, sales orders, quotes, products, leads, and deals through REST JSON APIs at region-specific endpoints. Authentication uses OAuth 2.0 Authorization Code flow with offline_access to obtain a refresh token, and access tokens valid for 1 hour must be refreshed automatically. Zoho CRM supports webhooks for push notifications on create/edit/delete events, but notification channels expire approximately every 24 hours and require automated renewal via PATCH /crm/v8/actions/watch. Notifications contain only record IDs; full payloads must be fetched via GET. Invoices, purchase orders, sales orders, quotes, vendors, and products are available only in Professional edition and higher, not in Free or Standard plans.

What moves between them

Business partners, contacts, and items from SAP Business One flow into Zoho CRM Accounts and Contacts. Sales orders and quotes from SAP are matched to Zoho deals and quotes for unified pipeline visibility. Closed deals in Zoho CRM are read back to match against SAP sales orders and invoices, closing the loop from opportunity to fulfillment. The sync runs on a schedule you define, with business partner and item synchronization occurring first to ensure reference data is ready before order records are processed.

How ml-connector handles it

ml-connector manages SAP Business One session tokens by logging in once and reusing the B1SESSION cookie for multiple requests, refreshing when the 30-minute inactivity timer approaches. On the Zoho side, it stores the refresh token encrypted and refreshes the access token transparently when calls return 401. Because SAP Business One is on-premise, you provide the full Service Layer endpoint URL per customer, including port. ml-connector polls both systems using OData filters and parameters; it accepts webhook events from SAP if Webhook Messenger Service is enabled, but does not require it. For Zoho, it refreshes webhook notification channels before expiry and fetches full payloads only for the records that changed. Business partners are matched by CardCode and mapped to Zoho Accounts; contacts are mapped by email address and CardCode. Sales orders are deduplicated by DocNum to prevent re-imports. On-premise SAP instances often use self-signed TLS certificates, which ml-connector accepts via customer configuration.

A real-world example

A mid-sized industrial distributor runs SAP Business One on-premise for order management and accounting, and Zoho CRM as the sales team's pipeline tool. Before integration, sales reps created orders in Zoho but finance staff had to manually re-key them into SAP, and business partner updates in SAP were never visible in Zoho until someone manually added them. Customer master data went out of sync, leading to shipping errors and missed revenue recognition. With SAP Business One and Zoho CRM connected, new customers created in SAP automatically appear in Zoho for sales reps, quotes and deals in Zoho flow back to SAP as sales orders, and the finance team sees order status in both systems without re-keying. The sales pipeline and the order book stay aligned.

What you can do

Sync SAP Business One business partners and contacts into Zoho CRM Accounts and Contacts, with deduplication by CardCode and email address.
Match Zoho deals and quotes back to SAP sales orders and invoices using order numbers and customer references.
Manage SAP Business One session tokens automatically, refreshing before timeout, and handle Zoho OAuth 2.0 with automatic token refresh.
Poll both systems on a schedule you control, with optional webhook support for SAP Business One v10.0 FP 2602 and Zoho notification channels.
Respect SAP Business One Professional edition constraints and Zoho CRM edition-based feature availability, with full audit trails and error recovery on every sync.

Questions

Which direction does data flow between SAP Business One and Zoho CRM?: Business partners, contacts, and items from SAP Business One flow primarily into Zoho CRM as Accounts and Contacts. Sales orders from SAP are matched to Zoho deals for unified pipeline visibility. Zoho deals and quotes are read back to match against SAP sales orders and invoices, closing the opportunity-to-cash loop. The integration is bidirectional for reference data alignment and unidirectional for transactional records.
Does ml-connector handle SAP Business One session tokens and Zoho OAuth refresh automatically?: Yes. ml-connector logs into SAP Business One once, reuses the B1SESSION cookie across requests, and refreshes before the 30-minute inactivity timeout. For Zoho CRM, it stores the refresh token encrypted, automatically refreshes the access token when calls return 401, and renews webhook notification channels before they expire every 24 hours.
What happens if SAP Business One is on-premise with a self-signed certificate?: ml-connector accepts self-signed TLS certificates on SAP Business One Service Layer via customer configuration and does not require a public CA certificate. You provide the full endpoint URL including port, and ml-connector validates it on first connection. Webhook Messenger Service activation on the SAP server is optional; polling with OData filters is the recommended default.

Connect SAP Business One and Zoho CRM

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started