Which CRM fits a lighter sales team: Salesforce or Frappe CRM
Frappe CRM fits lean pipeline teams that work mostly with leads, deals, calls and WhatsApp conversations, and that want quotes and customers in the same system as their ERP. Salesforce fits organizations that need its full ecosystem of custom objects, AppExchange packages, Apex automation and enterprise reporting. Most readers arriving here are facing a renewal, per-seat growth or a requirement to keep pipeline data on their own servers, so the first step is to decide which of those two profiles describes the sales team, not which product has more features. Start with the data model. If the team mainly tracks standard objects such as leads, accounts, contacts and deals, with a few custom fields, Frappe CRM covers that ground. If Salesforce runs approval chains, custom objects and flows that other departments depend on, list each one and confirm whether Frappe CRM has a direct equivalent or needs custom work through the Frappe Framework. The same applies to the sales hierarchy: Frappe CRM limits what users see through its own hierarchy settings, so check that model against the team's territory and forecasting rules before committing.
Two requirements often decide the question. The first is the ERPNext link. Frappe CRM can create an ERPNext quotation from a deal and create an ERPNext customer when a deal is marked Won or reaches a chosen status, but most of this syncing works only when both apps run on the same site. If quotes, invoices and stock must follow the sale in one system, an ERP-plus-CRM design fits. If the team quotes in Salesforce and invoices elsewhere, plan that integration explicitly. The second is the channel mix. Frappe CRM includes built-in Twilio and Exotel calling with call recording and WhatsApp messaging through the Frappe WhatsApp app. Confirm that the calling provider, number porting and recording rules meet local telecom and privacy requirements, and confirm the WhatsApp Business setup separately. Finally, ask whether the team can run the stack. Self-hosting Frappe CRM means someone must own upgrades, backups, the database, the background workers and security patches, and Frappe's supported versions policy ties warranty coverage to a listed version and a matching support plan. Salesforce removes that work but charges per user. Frappe Cloud is a middle path with per-site pricing that the product page describes as unlimited users, and it is worth comparing against a self-hosted deployment in your own cloud account.
Which option fits which sales scenario
This table matches common sales team situations to the option that usually fits better, based on the capabilities and limits covered on this page. Read each row against your own team size, integrations and reporting needs, and treat the reasons as the points to test in a proof of concept.
| Scenario | Better fit | Why |
|---|---|---|
| A small team running leads and deals only | Frappe CRM | Leads and deals with Kanban views, activities, tasks and calling through Twilio or Exotel are built in, and the app runs without an ERP stack. |
| A team that needs quotes and customers in ERPNext | Frappe CRM with ERPNext on the same site | Deals can create ERPNext quotations and customers, but most syncing only works when both apps run on the same site, so plan the hosting topology first. |
| A team dependent on AppExchange apps and Apex | Salesforce Sales Cloud | Frappe CRM has no AppExchange marketplace or Apex equivalent, so custom Apex logic and packaged apps need to be rebuilt or dropped before a move. |
| A team with heavy Salesforce reporting | Salesforce Sales Cloud, unless reports are confirmed | Verify that the report types, dashboards and forecasting your managers use exist in Frappe CRM before committing, because the supplied documentation does not cover them in depth. |
| A team that must self-host customer data | Frappe CRM | Frappe CRM can be self-hosted with the easy-install script, the ghcr.io/frappe/crm image or bench, and its AGPL-3.0 license places no per-user fee on the software itself. |
| Illustrative: a 10-person team that wants WhatsApp outreach | Frappe CRM | WhatsApp messaging runs through the Frappe WhatsApp app, so confirm the Meta business account setup and message template approvals with your own setup before go-live. |
| Illustrative: a team that relies on Salesforce Server Scripts for approval logic | Frappe CRM only after review | Frappe Framework Server Scripts are disabled by default from version 15 and must be enabled, and Frappe Cloud public shared benches do not allow them, so check hosting before rebuilding logic. |
Where the data lives and who controls it
Salesforce Sales Cloud runs only as a cloud service, so the hosting decision for Frappe CRM is the real trade-off to make. The cards below set out the hosting options, the identity choices and the restrictions that shape who controls customer records and how they are protected.
Salesforce runs only in the cloud
Sales Cloud is delivered as a vendor-hosted SaaS service, so your customer data sits in Salesforce's infrastructure under its subscription terms. You do not choose the server, the patch window or the storage location beyond what the contract and regional options allow. Frappe CRM changes that model because the same application can run in your own cloud account or data center. Before you decide, confirm which hosting regions and subprocessors your current Salesforce contract covers.
Frappe Cloud with usage billing
Frappe Cloud is a managed host for Frappe CRM with no per-seat charges, and the product page describes plans from 5 US dollars a month per site, billed by usage. Frappe states that customers are free to self-host or move to another provider, which keeps the exit route open. Ask Frappe which usage metrics drive the bill, how storage and backups are charged, and what export format and timing apply if you leave.
Self-hosting with the easy-install script
Frappe provides an easy-install script and the ghcr.io/frappe/crm container image, so your team can run CRM on servers it controls. You own the database, backups, TLS certificates, patching and monitoring, and those costs recur with the host. The Frappe Framework and CRM releases still need a planned upgrade path, so assign an owner for each update and test restores before going live.
Bench for development only
The bench command line tool is the development setup for Frappe apps, not a production deployment path. Use it to build custom fields, server logic or integrations in a sandbox, then move tested changes to a production host. Teams that skip this separation often edit production sites directly, which makes it hard to show a controlled change history during a review.
Social login and LDAP sign-in
Frappe documents Social Login Key for OAuth-style sign-in and an LDAP integration for ERPNext, which you should confirm applies to your Frappe CRM version and user directory. Salesforce customers usually connect Single Sign-On through Salesforce's own identity settings, so the sign-in path must be redesigned. Test how deactivated directory accounts lose access, since a stale session is a common finding in access reviews.
Server Script limits on shared benches
Server Scripts run Python on document events or as API endpoints, and from version 15 they are disabled by default and need the server_script_enabled setting. Frappe Cloud public shared benches do not allow them at all. If your Salesforce org relies on Apex-style logic, plan for a dedicated bench or a self-hosted site, and confirm the setting in your target version before you design workflows.
How per-seat licensing compares with flat hosting
Salesforce cost rises with every user you add, and it also rises when you move up an edition, because each tier changes the per-user rate and the features it includes. Each new seat, admin or integration user adds a line to the subscription, and add-ons such as extra storage or advanced packages add further lines. Ask Salesforce to state in writing the edition for each user role, the per-user rate for each one, the storage and API allocations included, and the price of every add-on you expect to need over the contract term. Ask whether the rates are fixed for the term or can change at renewal, and what notice period applies. Those answers let you model cost at your headcount in 12 months, not just today. Frappe CRM takes the opposite model. The Frappe CRM product page describes Frappe Cloud plans starting at 5 US dollars a month per site with unlimited users and no per-seat charges, billed by usage. Self-hosting removes that hosting fee entirely, but it moves the work to you or your partner. Your recurring costs become server capacity sized for peak concurrent use, backups stored off the server, the people who apply Frappe and CRM upgrades, and support. Confirm with Frappe which support plan matches the version you run, since warranty coverage depends on being on a listed version with a matching support plan.
The trade-off is not that flat hosting is free. Seat fees disappear, but someone must own sizing, the database and scheduler, backup restores, security patches and the upgrade calendar across Frappe and CRM. Test restores, not just backup jobs, and set a written owner for each task before go-live. Ask any implementation partner for a fixed-scope quote that lists these items separately: initial install and hardening, data migration, backup and restore testing, upgrade procedure, and ongoing support as a retainer. Also ask who pays for staging environments, which you need before every upgrade. Before you compare totals, check two things. First, confirm that the features you rely on, such as Twilio or Exotel calling, WhatsApp, Meta lead sync and the ERPNext quotation link, will run on the hosting you choose. Second, record the Salesforce add-ons you use today, because a seat-only comparison will understate the Salesforce side and overstate the self-hosted side. A short written comparison covering seats, add-ons, hosting, backup, upgrades and support gives procurement a fair basis for the renewal decision.
What each option costs to run, by component
Salesforce charges per user on a subscription, while Frappe CRM is free to self-host and its costs shift to hosting, setup and people. The cards below separate one-time work from recurring spend and name the drivers that move each line up or down, so you can build a quote that compares like with like.
Licensing and subscription
Frappe CRM is licensed under AGPL-3.0, so self-hosting carries no per-seat licence fee. Your Salesforce comparison should list every Sales Cloud seat, the edition and any add-ons, since these recur each year. On the Frappe side, check whether you want Frappe Cloud, which bills by usage with unlimited users and no per-seat charge, or a self-hosted site. Ask your vendor to confirm current edition pricing in writing before you build the model.
Hosting and infrastructure
Hosting is the main recurring cost of a self-hosted CRM. ERPNext pricing lists Frappe Cloud shared site hosting from 5 US dollars per month and Frappe Cloud servers from 20 US dollars per month for shared instances and 125 US dollars per month for dedicated servers. Self-hosting ERPNext is free, but you then pay for servers, backups, monitoring and staff time. Your main drivers are the number of sites, call recording storage and whether you need a dedicated server.
Implementation and setup
Setup is a one-time cost. It covers installing Frappe CRM with the easy-install script or Docker image, configuring email accounts, WhatsApp, Twilio or Exotel calling, and sales roles. If you use ERPNext, the setup also covers the shared site. Implementation is available through certified partners, so ask each bidder for a fixed-scope quote that lists each component and who performs it.
Data migration effort
Moving Salesforce data is a one-time project whose cost depends on record volume, custom objects and how much history you keep. Salesforce exports arrive as CSV files, and the ERPNext Data Import tool is advised for a few thousand records at a time, so large loads need batching and extra checks. Ask for the cost of cleansing duplicates, mapping fields and reconciling totals against the source before cutover.
Customization and integrations
Customization is recurring whenever your sales process changes. Salesforce automation often runs through Apex or flows that must be rebuilt, and Frappe CRM server scripts are disabled by default from version 15, so enabling them is a configuration decision with its own review. Quote custom fields, the Meta lead sync and any link to ERPNext quotations and customers separately, because most ERPNext syncing requires both apps on the same site.
Support and warranty
Support is the cost most often left out of comparisons. Frappe's supported versions policy says warranty coverage requires that you run a listed version and subscribe to a matching Frappe Cloud support plan. Version 14 reached end of life on January 31, 2026, so older deployments carry upgrade cost. Ask each provider which support tier covers security patches, and whether it covers your self-hosted version or only Frappe Cloud.
Internal admin time
Internal admin time is recurring and is often the largest hidden line. Someone must manage users, roles, the sales hierarchy, assignment rules, backups and upgrades, and apply minor releases that ship often. Salesforce admins are already on payroll, so the question is whether your team can absorb a Frappe administrator role or whether you buy that time from a partner on a retainer. Estimate the hours from your own environment rather than from a generic figure.
How the ERPNext link works for quotes and customers
When the link is active, a deal in Frappe CRM can generate an ERPNext quotation. Sales reps work the pipeline in the CRM, then produce the formal quote from the deal rather than retyping items, prices and customer details in a second system. The quotation then lives in ERPNext, where it follows the same document flow as other sales records.
- Source of truth: the deal holds the opportunity context, while the ERPNext quotation holds the commercial document that the customer receives.
- Item and price data: check how item codes, price lists and currencies in your deals map to ERPNext items before go-live.
- Document lifecycle: confirm who may edit a quotation after it is created and whether later changes flow back to the deal.
- Approval steps: if quotes need sign-off, confirm the approval workflow in ERPNext rather than assuming the CRM handles it.
- Testing: create sample deals in a staging copy and check the generated quotations line by line.
Ask the implementation partner to document the exact field mapping between deal and quotation in your environment.
The link can also create an ERPNext customer from a deal. According to the Frappe CRM ERPNext integration documentation, a customer can be created when a deal is marked Won or reaches a status you choose. This keeps customer master data from being typed twice and gives finance and operations a record to invoice against once a deal closes.
- Trigger status: decide whether Won alone or another stage should create the customer, and document that choice for the sales team.
- Duplicate control: check how the process handles an existing customer with the same name or tax number before a second record is created.
- Contact and address data: confirm which lead or deal fields populate the customer, contact and address records.
- Ownership: agree who maintains customer data after creation, since edits can occur in either app.
- Historical deals: decide whether deals already marked Won should be backfilled or left as they are.
Request a written list of the fields copied at creation and the trigger logic before you configure production.
Most of the syncing between Frappe CRM and ERPNext works only when both apps run on the same Frappe site. A site is a separate database and application instance inside a Frappe bench or deployment. If the CRM and ERPNext sit on different sites, many of the quote and customer flows will not function as described, so this is a design decision to make early.
- Shared deployment: both apps must be installed on the same site, which affects how you size and back up the environment.
- Version alignment: the stable Frappe CRM v1.x branch targets Frappe and ERPNext versions 15 and 16, so the two apps must match a supported pair.
- Upgrade coupling: an upgrade to the shared site touches both apps, so plan a maintenance window and a test upgrade.
- Multi-entity setups: separate legal entities or regions that need separate sites will need a different integration approach, if one exists.
- Hosting options: Frappe Cloud and self-hosted deployments both support the shared-site model, so confirm the layout with your partner before purchase.
Confirm the site topology, version pair and upgrade plan with your implementation partner before committing to the design.
ERPNext is a full ERP covering accounting, order and inventory management, manufacturing, asset management and projects. The link is valuable when you need those modules alongside the CRM. If your sales team only needs pipeline tracking, calling, messaging and contact management, running ERPNext adds accounting and stock components that someone must configure, secure and maintain.
- Accounting ownership: if invoicing and the general ledger already sit in another system, ERPNext would duplicate that role.
- Inventory needs: teams that sell services or do not track stock may never use the ERPNext item and warehouse features.
- Administration effort: every ERPNext module carries configuration, user roles and data quality work that a CRM-only team does not need.
- Standalone CRM option: Frappe CRM can run without ERPNext, so the decision should follow your process map rather than the app list.
- Future growth: if quoting or finance requirements are likely soon, weigh the cost of adding ERPNext later against running it from the start.
List the ERP functions your business needs in the next few years before deciding whether the ERPNext link is worth the added scope.
What moving from Salesforce to Frappe CRM involves
The sequence moves pipeline data, sales process and access rules out of Salesforce and into Frappe CRM in a way that the sales team can verify record by record before the old system is switched off. Each step ends with a check that the team can sign off.
Inventory objects, automation and integrations
List every Salesforce object in use, including leads, accounts, contacts, opportunities, tasks, activities and any custom objects, along with the fields, record types, page layouts, reports and dashboards that depend on them. Record each Apex class, flow, process, approval step and AppExchange package, and note which ones the sales team relies on daily. The client's Salesforce administrator and a sales lead should sign off the list, because it becomes the scope for everything that follows. Done means every object and automation has an owner and a keep, redesign or retire decision.
Confirm what the export leaves out
Before extracting anything, confirm with Salesforce documentation and your own org which data types the chosen export method omits. The Data Export Service produces CSV files in a compressed archive and runs on a weekly or 29-day cadence depending on edition, so the team should check its settings and attachment options against the list from the first step. Data Loader is a separately installed client that supports scripted, repeatable exports. Done means a written gap list exists, covering items such as email content, files, attachments and integration data, with a plan for each gap.
Export records and map them to Frappe CRM
Extract leads, accounts, contacts, opportunities and tasks as CSV files, then build a field map that links each Salesforce field to a Frappe CRM lead, deal, organization or contact field, including custom fields that must be created first. Decide how owners, stages and currencies translate, and where a Salesforce account and its contacts will sit in Frappe CRM. Check the mapping against a sample of a few dozen records that sales reviewers know well. Done means the sample imports with the expected owners, stages and history references.
Import in batches with the ERPNext Data Import tool
Use the Data Import tool in ERPNext, which reads CSV or Excel files with downloadable templates and supports child table rows. The ERPNext documentation advises importing only a few thousand records at a time, so split the full extract into batches and import them in a fixed order, starting with organizations and contacts, then leads and deals. A DeployOpen engineer or the client's administrator logs each batch with its record count and any rejected rows. Done means every batch reconciles against the Salesforce export totals and rejected rows have a documented fix.
Rebuild assignment rules, templates and access
Recreate the lead assignment rules, email accounts and email templates that the sales team used in Salesforce, and set up the sales hierarchy so that users see only the records their role allows. Assign the Sales User, Manager and Admin roles deliberately, and test each role with a real user account in a staging site. Where Salesforce logic lives in Apex or flows, redesign it using Frappe CRM features, and treat any Frappe Server Script as a controlled change, since it is disabled by default from version 15 and must be enabled in settings. Done means each role has signed off the access test and every rebuilt rule has a named owner.
Run both systems in parallel
Keep Salesforce active for a defined overlap period while a pilot group works in Frappe CRM on live opportunities. Reconcile pipeline totals, stage counts and owner assignments between the two systems each week, and log any discrepancy with its cause. Ask the team to report calling, WhatsApp and web form issues, since these channels depend on integrations that Salesforce may have handled differently. Done means reconciliation differences are explained and the pilot group confirms it can run its daily pipeline in Frappe CRM.
Cut over and retain the Salesforce archive
Freeze Salesforce data entry for the affected teams, run a final incremental export and import, and point users, phone numbers, Meta lead forms and web forms at Frappe CRM. Store the final Salesforce export and its checksums in the client's own archive, since the Salesforce export link is time-limited and the export is the only copy of excluded data once licenses end. Confirm the Frappe CRM backup schedule and restore test before the old system is closed. Done means the cutover checklist is signed by the business owner and the archive restore has been tested.
Questions buyers ask before switching from Salesforce
How much effort does a migration from Salesforce to Frappe CRM take?
The effort depends mostly on how much custom configuration you have in Salesforce, not on the number of users. A team that uses standard objects such as accounts, contacts, leads and opportunities has a small mapping job. Teams with many custom objects, custom fields, record-triggered automation, approval processes or AppExchange packages need to rebuild each of those pieces in Frappe CRM, which is where most of the hours go. Other drivers include the volume of historical activity you want to keep, the number of users who need training, and whether you also move quoting and customers into ERPNext. Ask any implementation partner for a written estimate that lists each Salesforce object, field and automation, and confirm with Frappe which features in your Salesforce org have a direct counterpart before you start.
How long does a Salesforce to Frappe CRM migration usually take?
No researched duration is available for this migration, so treat any single number you see as unverified. The timeline is set by the size of your data, the number of custom objects and automations to rebuild, and how many parallel-running weeks your sales team needs before cutover. Data extraction is quick when standard objects are involved, but cleaning duplicate contacts and accounts often takes longer than the technical import. Plan for a period where Salesforce and Frappe CRM run side by side, and agree on a cutover date only after your sales managers have tested their pipeline views. Ask your implementation partner for a fixed-scope plan with milestones, and confirm the Frappe CRM version you will deploy so the plan matches the release you run.
Can our internal team run a Frappe CRM migration without outside help?
A team with someone comfortable with Linux servers, Docker or the bench command line, and with Salesforce data exports, can often handle a simple pipeline migration in-house. The harder parts are hosting, backups, upgrades and anything involving custom scripts. Server Scripts in Frappe are disabled by default from version 15 and must be enabled with the server_script_enabled setting, so any Salesforce logic you want to rebuild as server-side code needs an administrator who knows that restriction. Also check whether your team has the time to maintain the system after go-live. Decide which parts you will own and which you will buy as a fixed-scope engagement, and confirm the skills needed with Frappe documentation and your own staff.
Which Salesforce features have no direct equivalent in Frappe CRM?
Frappe CRM covers leads and deals, Kanban and custom views, activities, notes, tasks, calling, WhatsApp messaging, web forms, lead syncing from Meta ads, assignment rules, a sales hierarchy and email templates. Check carefully for features beyond that scope, such as the depth of Salesforce reporting and dashboards, Apex code, AppExchange packages, Salesforce-specific flows and some forecasting or CPQ functions. Frappe CRM also depends on the Frappe Framework, so custom logic is written against that framework rather than Salesforce's platform. Make a written list of every Salesforce feature your sales team uses weekly and ask Frappe which of them have a direct equivalent, a workaround or no support.
How do upgrades and warranty coverage work for Frappe CRM?
Frappe publishes a supported versions page, and its policy says customers must run a listed version and hold a matching Frappe Cloud support plan to receive warranty coverage from Frappe. Frappe CRM's stable v1.x branch is compatible with Frappe and ERPNext versions 15 and 16, so your Frappe Framework version determines which CRM releases you can run. Released versions change frequently; for example, v1.87.0 arrived on October 9, 2026 and v1.88.0 on October 15, 2026. Self-hosted deployments remain your responsibility for testing and applying updates, backups and rollback. Confirm the warranty terms, the support plan that matches your deployment and the upgrade path for your chosen version directly with Frappe before signing any contract.
Does Frappe CRM handle phone calls and WhatsApp for sales teams?
Yes, Frappe CRM includes built-in calling through Twilio and Exotel with call recording, and WhatsApp messaging through the separate Frappe WhatsApp app. Each channel needs its own provider account, credentials and configuration, so the cost and setup of telephony and WhatsApp Business access sit outside the CRM itself. Check which country codes, phone numbers and call routing rules your business needs, and whether your telephony provider is supported in your region. Confirm the exact provider options, recording storage rules and WhatsApp Business requirements with Frappe documentation and your telephony and messaging vendors before you commit.
What does a Frappe CRM deployment cost compared with Salesforce licenses?
Frappe CRM is licensed under AGPL-3.0, so the software itself has no per-user fee. Your costs come from hosting, implementation, data migration, support and internal administration time. Frappe Cloud plans start at 5 US dollars per month per site with unlimited users, according to the Frappe CRM product page, and self-hosting avoids that charge while adding server and maintenance costs. Salesforce costs recur per user and per edition, so the gap widens as headcount grows. Build a multi-year model that lists each component, who is paid for it and what recurs, then request quotes that separate one-time migration work from ongoing support.
What to confirm before committing to either platform
Start with the exit terms in your Salesforce contract, because they decide how cheaply you can leave whatever you choose. Confirm in writing which export routes your edition and contract give you. The Data Export Service runs weekly in Enterprise, Performance and Unlimited editions and every 29 days in Professional and Developer editions, so a team on a lower edition may have to plan its cutover around that cadence. Ask whether attachments, files and custom objects are included in the export you will actually use, and whether your agreement limits bulk extraction or API access during a transition period. Get those answers from your account executive and your legal team before you sign a Frappe CRM implementation, not after.
On the Frappe side, pin the version and check compatibility before you plan the build. Confirm the latest release on the frappe/crm releases page and verify that your ERPNext and Frappe Framework versions fall within the range the stable v1.x branch supports, which the README lists as versions 15 and 16. If you run ERPNext, check the support status of your major version on Frappe's supported versions page and confirm whether you need a Frappe Cloud support plan for warranty coverage. Calling and WhatsApp are not free of third-party dependencies: the built-in calling supports Twilio and Exotel, so your telephony and WhatsApp Business accounts, numbers, consent records and per-message charges belong to you and must be contracted separately. Ask your implementation partner to test call recording and WhatsApp delivery on a staging site before rollout.
Finally, confirm identity and compliance scope before you rely on either platform for regulated customer data. Decide whether single sign-on will run through an identity provider you already operate, and check the social login and LDAP options against your directory design and role mapping to Sales User, Manager and Admin. Ask Frappe or your partner which parts of the deployment, such as hosting, backups, access logs and subprocessors, the evidence covers, and which remain your responsibility. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports or certifications. Those come from independent auditors and certification bodies, so the scope you agree in writing should name exactly what each party provides.
How DeployOpen helps evaluate, implement or migrate
DeployOpen starts from your pipeline, your calling and messaging needs, and whether quotes and customers must sync with ERPNext. We then plan, build, test and document a self-hosted Frappe CRM inside your own infrastructure, and hand it over with runbooks your team can operate.
How we scope
- Engagements are fixed-scope, with the scope, deliverables and timelines agreed in writing before work starts.
- The written scope lists which pipeline stages, lead sources, calling and WhatsApp channels and sales roles must work at go-live.
- We confirm whether the ERPNext link is needed, since most quote and customer syncing requires both apps on the same site.
- We record which Salesforce reports, automations and integrations are kept, replaced or retired, so nothing is dropped silently.
How we build
- We install Frappe CRM on infrastructure you control, using the deployment method that fits your cloud account or data center.
- We configure lead assignment rules, the sales hierarchy, web forms, email accounts and templates to match your sales roles.
- We connect calling and WhatsApp providers, and test call recording and message flows with your team before cutover.
- We review any custom server logic against the access restrictions that apply to Frappe Cloud shared benches and recent Frappe versions.
How we hand over
- We map Salesforce exports to Frappe CRM fields and run test imports, reconciling record counts and ownership before any live load.
- We document the architecture, configuration, backup steps, user roles and the open items agreed in the written scope.
- We run a parallel period with your sales team, then agree a cutover date and a retirement date for the Salesforce org.
- We provide training material and admin runbooks so your staff can manage users, rules and upgrades without us.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer, sized to the scope you agree.
- We plan Frappe CRM upgrades against the supported version policy and test them in a staging environment first.
- Ask any provider to confirm which Frappe and ERPNext versions are on their support list before you sign.
- Compliance evidence we prepare covers your own controls and records; independent auditors issue any audit reports or certifications.
