The team that builds the product runs the rollout — and puts the date in writing.
We handle migrations for teams coming from Dynamics 365. This page sets out how we deliver, what we can measure and where our limits are. We have no formal partnership with Microsoft.
The short answer
We do not compare ourselves with another product on this page. We write what we do and what we don't do.
This is how we deliver. Discovery, configuration, data migration and training are run by the team that builds the product; there is no separate consulting project in between. We don't commit to a timeline before discovery; after the discovery call we give you a date, not a range.
When you evaluate any proposal, put setup, customisation and training next to the licence line. Without those lines two proposals aren't being compared on the same scale.
How Rapitek CRM works
| Area | Rapitek CRM |
|---|---|
| Time to go live | No timeline committed before discovery; after discovery a date in writing, not a range |
| Who does the rollout | The team that builds the product |
| Microsoft ecosystem | We connect over standard APIs. Outlook and Microsoft 365 connections are not available today; we have no built-in integration with Teams or Power BI |
| Inside the product | |
| Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery |
| Support and training language | Turkish |
| Licensing structure | Three tiers, per user, prices published |
| Data location | European Union: database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany) |
| Data separation | A separate database per customer |
| Ecosystem breadth | Narrow. We have no app marketplace and no trained partner network — we say so plainly |
| Multi-region enterprise operations | Not our focus; we are not positioned for multi-region, multi-entity enterprise operations |
Where the difference shows at mid-market scale
A date, not a range
After the discovery call we give you a date, not a range, for the move from discovery to go-live. You don't have to manage a long consulting project.
Shared WhatsApp inbox
The team writes from a single work number; every message is logged on the customer record and the history stays with the business.
Turkish ERPs
Per-project connections to Logo, Netsis, Mikro and Paraşüt — and the same method for SAP and Oracle.
A separate database
A separate database per customer — not a row filter in a shared table.
Connect your own AI
Your CRM is open over MCP; you connect your own Claude account and access stays capped by that user's permissions.
Predictable licensing
Three tiers, per user per month, prices written on the page. No module matrix to decode.
When we are not the right product
- If you are deeply invested in the Microsoft ecosystem. If you work through Teams, report in Power BI and manage identity with Azure AD: Outlook and Microsoft 365 connections are not available today, and we have no built-in integration with Teams or Power BI.
- If you run a multi-region, multi-entity structure. Enterprise requirements at that scale are not our focus.
- If you want ERP and CRM under one roof. We don't have an ERP side; we connect to your existing ERP instead.
- If you are looking for an app marketplace and a broad partner network. We have no app marketplace and no trained partner network.
- If your procurement runs through an existing enterprise agreement. We are not a party to such an agreement.
About migrating from Dynamics 365
Can our Dynamics data be migrated?
Do you work with Teams and Outlook?
How much does Rapitek CRM cost?
How long does the migration take?
Let's map the scope and the timeline together.
In a 30-minute call we listen to your current setup and talk through whether a migration is realistic. If it isn't, we'll say so.
30 minutes · No obligation · The call is held in Turkish
