Your ERP stays where it is; the CRM talks to it.
Account, balance, order and invoice data stays in the ERP; your sales team sees the same data in the CRM. We build the connection ourselves, using the REST API, webhooks and import/export. This page describes the framework that stays the same whatever your ERP is called.
ERP and CRM do not do the same job: where exactly is the line?
The debate between ERP and CRM comes from the fact that both systems use the same words. Both have a “customer”, both have a “product” and a “price”, but they do not mean the same thing.
- The ERP records work that has already happened. The order was entered, the goods shipped, the invoice issued, the payment collected. The accuracy of the record carries financial and legal consequences; that is why an ERP is conservative, and it should be.
- The CRM records work that has not happened yet. Who called, what was discussed, which quote was given, why it was lost. A record here is not a document but a possibility; it is normal for it to change often.
- The gap sits between the two. One question sums it up: when does the person writing the quote find out that the company across the table has an overdue balance? The ERP knows this; the person writing the quote does not.
Integration work means closing that gap, and it is finished when four questions are answered: which field, in which direction, how often, on which key. The fourth is less visible than the other three, because its answer only emerges once you put the records side by side: which field matches the same company across the two systems? In our own installations that field is the tax identification number, not the trade name, because a name can be written “A.Ş.” in one system and “AŞ” in the other, and a match built on the trade name disappears silently.
We draw up this four-line table in the discovery call and hand it over in writing; if a line stays empty, we write it down as empty. When an empty line gets filled in halfway through the project, the field mapping and testing done up to that point have to be revisited. We have seen this in our own projects. That is why the table is filled in before the work starts.
Why is the connection built for your installation?
We build every ERP connection specifically for your project. The connection is built as an integration project whose scope is determined in the discovery call, using the REST API, webhooks and import/export.
This surface is usable from outside: ERP integrators can read and write records through this same REST API.
These are the tools we have:
- REST API: every record in the CRM, from lead to quote, from invoice to task, can be read and written through it, and you can read the field structure from outside. Access is granted with permissions, without sharing passwords; up to 25 operations can be sent in a single request, and bulk transfers handle up to 200 records per request.
- Outbound webhooks: your system is notified when a record is created or changed; the receiving system can verify the notification came from us and reject forged ones, and a notification that does not arrive is retried.
- Import: a four-step wizard: upload, map fields, preview, run. More than 75 objects are supported; there is a limit of 10 MB per file and 100,000 rows per job, and you confirm the mapping on screen. Export is done in the same module.
So why is the connection designed separately for each customer? Because access on the other side changes from installation to installation: the ERP's version, the licence scope, which modules were bought and where the system runs, on-premise server or hosted, determine the method.
For the general framework, see the integrations page. We also cover how the same framework looks for a single ERP on our Netsis integration page, and, for readers who want the two paths side by side with a decision criterion, on a separate page comparing a built-in connection with a project-specific integration.
Wednesday, 10:40. IT, sales and finance around the same table in the discovery meeting. Six decisions come out of it:
-
1
Each field's authority is assigned to one side
Trade name and tax number stay in the ERP; conversation history and quotes stay in the CRM. No field is left with two owners: if the same field is updated independently in two places, nothing decides which value is valid when the two diverge.
-
2
The matching key is chosen, the exceptions listed
The tax identification number is taken as the key; the trade name is used only for verification. A list of records with no key is drawn up, and the meeting decides whether they should be merged or left to be handled manually.
-
3
The direction of flow is written down field by field
Balance flows from the ERP to the CRM; the order details of a won opportunity flow from the CRM to the ERP. If a field is to work in both directions, the conflict rule, which side wins in a contradiction, goes on the same line.
-
4
Frequency is a business decision, not a technology preference
Balance visibility can be achieved with a daily transfer; if it needs to be closer to the event, the method shifts to the REST API and webhooks. As frequency goes up, scope and cost change, which is why the business side makes this call.
-
5
Whether the ERP can be reached from outside is answered
If there is access, we talk about the REST API; if not, the flow is built on periodic import/export. Both work; the difference is latency and maintenance load. If the access conditions change later, the same scope moves onto an API-based flow.
-
6
Who will write the connection is decided
Both paths are open: we write the connection, or your partner who knows the ERP side writes it themselves over that same REST API. In the second case we provide the field structure, the access permissions and the field mapping table.
Flows that can be built between the ERP and the CRM
Account matching and duplicate clean-up
Accounts in the ERP are linked to company records in the CRM using the tax identification number as the key. Records whose key does not match are filtered out during setup; the matching rule lives in the written scope, not in someone's memory.
Visibility of balance, due dates and credit limit
Fields such as open balance, overdue amount and credit limit are transferred onto the company record. The transfer frequency (daily, weekly or periodic) is set in the scope, and the values are visible on the quote screen.
Tracking document data
Order and invoice headers are tracked as a list on the company record. Authority over the document stays in the ERP; the CRM does not produce documents, it adds a visibility layer for the sales team.
Product and price list transfer
When product records and the price list are transferred from the ERP to the CRM, quotes are written at the current price. The transfer can be periodic or set up over the REST API; authority stays in the ERP.
Passing a won opportunity to the ERP side
A webhook that passes the order details to the external system when an opportunity is won can be set up. Entering the same data a second time by hand on the accounting side is reduced; which fields are sent is written into the scope.
Defining the CRM equivalent of ERP fields without writing code
An administrator defines the CRM-side equivalent of fields such as credit limit, payment terms, dealer code or region without writing code. Adding custom fields and custom objects is standard in the product.
Four methods: which one, when?
| Method | What it does | When it is preferred |
|---|---|---|
| REST API | An external system reads and writes every record in the CRM; access is granted with permissions, the field structure is read from the API, and up to 25 operations can be sent in one request | When suitable access exists on the ERP side and the flow is expected to run close to the event |
| Outbound webhook | Events in the CRM are notified to the external system; the receiving system can verify the notification came from us, and a notification that does not arrive is retried | For flows that need notification from the CRM towards the ERP, if the ERP side has an address that can receive it |
| Import (Data Hub) | Excel/CSV extracts are transferred with a four-step wizard: upload, map fields, preview, run. 75+ objects, 10 MB per file, 100,000 rows per job. Export is done in the same module | It requires no API access on the other side, so it can be started before the access question is answered; when a periodic sync is enough, or when the ERP cannot be reached from outside |
| Third-party integrator | Your partner who knows the ERP side can write the connection themselves using that same REST API; we provide the field structure, the access permissions and the field mapping table | When you want to keep working with the firm that implemented your ERP |
What we have verified
How an ERP connection is put live
-
1
Discovery and access assessment
We establish your ERP's version, licence scope, which modules you use and where the system runs. We recommend that the partner who implemented your ERP, or your IT lead, joins this call; they hold the answer to the access question.
-
2
Field mapping table and written scope
Which field flows in which direction, how often, and the conflict rule are written line by line. The method is chosen here; the scope and any cost are shared in writing before work starts. The table is filled in first and the work starts after, so no surprise item appears.
-
3
Configuration and a test transfer with sample data
Fields, lists and permissions on the CRM side are set up; a test transfer is run with a sample of a real extract. Matches are verified on the key field, duplicate records are filtered out and faulty rows are reported.
-
4
Training, go-live and maintenance responsibility
Team training and close follow-up in the first week. Who updates the mapping table when a field or version changes in your ERP is written into the scope; when a flow stops, you know who to contact.
Scope and setup conditions
-
1
Stock stays in your ERP or warehouse system
Authority over the stock record stays in your ERP or warehouse system. We build a visibility layer in the CRM with a defined scope.
-
2
Quote → order → collection tracking is linked in the CRM
The chain can be switched on or off per installation; turning a quote into an order runs through a built-in action. The accounting record stays in your ERP.
-
3
Production: bill of materials and line definition are in the product, MRP runs in your ERP
Bill of materials, production line and work order screens are in the product; production planning runs in your ERP.
Scope comes out of discovery; plan prices are in the open
The cost of an ERP connection depends on data volume, the direction of the flow and the access available on the other side; it is shared in writing after discovery. We publish plan prices and separately priced items on a single page.
Three plans, a scope table and separately priced items on one page.
Frequently asked questions about ERP–CRM integration
We already have an ERP. Why would we need a CRM?
What does ERP CRM integration mean in practice, what actually gets done?
Is there a ready-made ERP module in Rapitek CRM?
Can an outside ERP integrator use this API?
Which ERPs do you work with?
Which field is used to match companies across the two systems?
Our ERP server cannot be reached from outside. Is integration still possible?
Can our own ERP partner write the integration?
Why does stock stay in the ERP?
Can we issue e-Fatura from the CRM?
Is synchronisation real-time?
How is the cost of the integration determined?
How long does implementation take?
Will we lose data when we move our ERP data into the CRM?
Where is our data held?
Is your ERP on this list?
Netsis integration
Which direction account, balance, order and invoice data flows in; choosing a method for an installation running on an on-premise server.
Nebim integration
How the retail and wholesale channels are kept apart in the same CRM; the flow of dealer balances and the seasonal price list.
Logo integration
Scope for installations using Tiger, Go and j-Platform; the effect of a version upgrade on the field mapping table.
Mikro integration
Connecting to the commercial and accounting software: account records, balance and invoice data visible on the sales screen.
SAP integration
Scope, choice of method, and written answers to the security questions IT will ask.
Paraşüt integration
The pre-accounting side: account and collection visibility; where e-Fatura information appears in the CRM.
Luca integration
How the flow is built when your accounting sits with your financial adviser, and the scope of periodic transfers.
Built-in connection or project?
The decision criterion: when a connection configured during setup is enough, and when a project-specific integration is required.
Integrations
The connections working in the product today and the ones we build on request; a short summary of our scope and setup conditions.
Security
Which country the data sits in, the list of sub-processors, backups and audit trail.
Let's answer the four questions together in 30 minutes
Which field, in which direction, how often, on which key. Fill in the form and we'll open your 7-day trial account and send you your login details; no credit card required. If you like, in a 30-minute intro call we start filling in this table against your own ERP and choose the method and the scope together.
