Which PHP CRM fits a smaller team: EspoCRM or Krayin?
EspoCRM fits a small team that needs OpenID Connect or LDAP sign-in at launch. EspoCRM documents OIDC sign-in since version 7.3, with optional user creation on first login, mapping of identity provider groups to teams, backchannel logout and a fallback login method, and it also describes LDAP authentication for Active Directory and OpenLDAP. Its AGPL-3.0 license is acceptable if your organization does not object to copyleft terms for a tool it runs internally, and workflows and business process management come from the paid Advanced Pack, which is included in all EspoCRM Cloud plans. Note that EspoCRM's own two-factor authentication is not compatible with OIDC, so confirm how your identity provider will enforce multi-factor sign-in before you commit.
Krayin fits a team that prefers the MIT License and already runs Laravel. Krayin's README states the project will always be free under MIT, and its stack is Laravel with a Vue.js front end, so in-house PHP developers can maintain it directly. Krayin's README and website do not document SAML, OpenID Connect or LDAP sign-in for the core CRM, so single sign-on has to be built through custom development or added through an extension. If sign-in can wait, or your team is willing to own that build, Krayin's MIT terms and Laravel fit may outweigh EspoCRM's ready-made identity options.
The decision turns on three questions. First, does sign-in have to work on day one through your existing identity provider? Second, do you need reports, workflows or BPM, which EspoCRM sells as paid extensions, and do you want a vendor-supported path for them? Third, does your team have deeper skill in PHP with Laravel or in the EspoCRM configuration model? Confirm Krayin's current support options and the cost of any custom SSO work in writing with its vendor, and check EspoCRM's OIDC documentation against your identity provider's group and logout settings in a test instance before you choose.
Which scenarios favor EspoCRM and which favor Krayin
This table maps common team scenarios to the platform that fits each one better, with the condition that drives the choice. Read each row against your own identity, hosting and workflow requirements, because a paid extension or custom build can change the answer. Neither platform wins across the board; the right choice depends on which constraint your team cannot change.
| Scenario | Better fit | Condition that drives it |
|---|---|---|
| SSO required on day one | EspoCRM | OIDC sign-in since version 7.3, with group-to-team mapping. Krayin's core has no documented SSO, so it needs custom work or an extension. |
| Workflow automation needed | EspoCRM | Workflows and BPM come from the paid Advanced Pack, included in cloud plans. Confirm which workflow options Krayin offers before deciding. |
| Team strongest in Laravel and Vue.js | Krayin | Krayin follows Laravel conventions and Composer installs. EspoCRM customization uses its own Entity Manager and Formula Script. |
| Multi-tenant SaaS delivery | Krayin | The paid Multi Tenant SaaS extension lets tenants share one instance with isolated data. Confirm EspoCRM's tenancy model before choosing it for this use. |
| Vendor-managed hosting | Depends on headcount | Krayin Cloud Hosting is listed at 20 US dollars a month with unlimited users (krayincrm.com). EspoCRM Cloud bills per user, with minimums of 3 to 10 users by plan. |
| Existing MariaDB 10.6 or 10.11 estate | EspoCRM | EspoCRM supports MariaDB 10.6 or later. Krayin's README requires MariaDB 11.4 LTS or higher, so older database servers need an upgrade first. |
How EspoCRM and Krayin are built and what that means for operations
EspoCRM and Krayin both run on PHP and both are self-hosted, but their stacks, installers and runtime needs differ in ways that shape patching, backups and who on your team can run them. The cards below cover the components each one depends on and the operating decisions that follow.
EspoCRM runtime and database choice
EspoCRM supports PHP 8.3 to 8.5 on Apache, Nginx or IIS, with MySQL 8.0 or newer, MariaDB 10.6 or newer, or PostgreSQL 15 as the database. Your team picks the database at install time, so the choice should match the skills and backup tooling you already run. Confirm the exact PHP extensions and web server settings for your chosen combination in the server configuration docs before you build the image.
EspoCRM cron for background jobs
EspoCRM needs cron or a scheduled task to run background jobs such as scheduled workflows and maintenance tasks. If that scheduler is not configured, time-based behavior silently stops, which is easy to miss in a small deployment. Add a check for the scheduler to your monitoring and confirm the job setup during acceptance testing.
EspoCRM install script and command.sh
The installation script for Ubuntu, Debian and Linux Mint deploys a Docker-based stack with Nginx and MariaDB, with optional Let's Encrypt certificates. Its command.sh utility handles backups, restores and upgrades. This suits a team that wants a documented starting point, but you still own the host, the container images and the restore tests, so confirm the script's assumptions against your own hardening baseline.
Krayin on Laravel and Vue.js
Krayin is a Laravel application with a Vue.js front end, installed with Composer and the php artisan krayin-crm:install command. Your team needs PHP and Laravel familiarity, plus Composer for dependency work, which is a different skill set from a PHP CRM that ships as a packaged application. Ask the Krayin maintainers which Laravel version the current release targets before you plan upgrades.
Krayin host requirements and memory
Krayin requires PHP 8.3 or higher, Composer 2.5 or higher, MySQL 8.0.32 or higher, or MariaDB 11.4 LTS or higher (11.8 LTS recommended), with Apache 2 or NGINX and at least 3 GB of RAM. Those are minimums stated in the README, so size the host for your user count and confirm the figure in a load test before you commit to a VM size.
Patching and who can run each
EspoCRM's packaged installer and upgrade utility suit a generalist platform administrator who can follow a runbook. Krayin's Composer-based deployment suits a team with a PHP developer who can handle framework updates, dependency conflicts and schema changes. Decide who owns each patch cycle before you choose, and ask Krayin whether a Docker image is maintained for your version path.
Where single sign-on sits in each CRM
EspoCRM ships single sign-on in the free core, while Krayin does not document it. EspoCRM supports OpenID Connect sign-in since version 7.3, with optional user creation on first login, mapping of identity provider groups to EspoCRM teams, backchannel logout and a fallback login method. Its documentation also describes LDAP authentication, including Active Directory and OpenLDAP. One constraint matters for planning: EspoCRM's own two-factor authentication is not compatible with OIDC, so the identity provider has to carry the second factor. Krayin's README and website do not document SAML, OpenID Connect or LDAP sign-in for the core CRM. Any SSO for Krayin therefore has to come from custom development or a third-party extension.
The gap matters most when your identity provider is the control point for access. That is typical when joiners and leavers are managed in Active Directory or a central IdP, when group membership should decide which sales territory or team a user sees, or when an audit requires that disabling a directory account also removes CRM access. In EspoCRM, group-to-team mapping and backchannel logout cover much of that without custom code, though you still need to test the mapping against your own group design. For Krayin, a delayed or partial SSO build becomes a standing cost, because every upgrade may need the integration retested. If you run Krayin in a regulated environment, plan an access review that does not rely on SSO until the integration exists.
Before you decide, ask Krayin for written confirmation of any SAML, OpenID Connect or LDAP support in the core, the name and version of any extension that provides it, and the upgrade path for that extension. Ask EspoCRM to confirm how OIDC behaves with your identity provider's multi-factor setup and which fallback login you would keep for break-glass access. Test both in a non-production instance with a real leaver scenario: disable an account in the directory and confirm the CRM session ends. Consult the EspoCRM OIDC documentation for the settings to review with your identity team.
Feature and capability comparison for EspoCRM and Krayin
This table compares the two CRMs on the capabilities that most often decide a smaller team's shortlist, using only the feature claims we can source. Where a capability is not documented for Krayin, the cell says what to confirm rather than assuming it is missing, so check those rows against the current release before you decide.
| Capability | EspoCRM | Krayin CRM |
|---|---|---|
| License | AGPL-3.0 core, free to download and self-host; paid official extensions sit on top | MIT License, with the project stating it will always be free under MIT; paid extensions are sold separately |
| Core sales features | Free core covers CRM records and standard sales data; products, quotes and invoices come from the paid Sales Pack | Lead and opportunity tracking, deal management, sales forecasting, contacts, activities and products with inventory tracking, per the Krayin website |
| Reports and workflows | Reports, Business Process Management and workflows are in the paid Advanced Pack, which is included in all EspoCRM Cloud plans | Confirm whether reporting, workflow automation and BPM are included in the core or need an extension or custom work |
| Scripting | Formula Script is built in and runs in before-save scripts, API before-save scripts, workflows and BPM | Not documented in the supplied material; confirm whether any scripting or rules engine exists in the core release |
| API authentication | API key, HMAC and basic authentication through dedicated API users with role-based permissions; HMAC is the most secure method and basic is not recommended | Confirm the REST or API authentication methods and how API access is scoped in the current release |
| SSO and LDAP | OpenID Connect since version 7.3, with first-login user creation, group-to-team mapping and backchannel logout; LDAP covers Active Directory and OpenLDAP; EspoCRM's own 2FA is not compatible with OIDC | SAML, OpenID Connect and LDAP are not documented for the core CRM; single sign-on would need custom development or an extension |
| Multi-tenancy | Not listed as a core feature in the supplied material; confirm with EspoCRM before planning shared instances | Multi Tenant SaaS paid extension lets several tenants share one instance with isolated data |
| Managed hosting | EspoCRM Cloud per-user plans (Basic, Enterprise, Ultimate) with US and German server locations noted in the related planning material | Fully managed Krayin CRM Cloud Hosting, advertised at 20 US dollars a month with unlimited users on the Krayin website |
| Product inventory | Inventory is in the paid Sales Pack | Products with inventory tracking are listed on the Krayin website as part of the core feature set |
What is free and what is paid in each platform
EspoCRM is licensed under AGPL-3.0, and the open-source edition can be downloaded and self-hosted for free. The free core covers the CRM itself, including the self-hosted installation. Paid value comes from official extensions and from the cloud service, so the cost picture depends on which features your team needs.
- Free core: The open-source edition can be downloaded and self-hosted at no license cost. You still pay for the server, the database, backups and the staff who run them.
- Advanced Pack: Adds reports, Business Process Management and workflows. It is included in all EspoCRM Cloud plans, but for self-hosting it is a separate purchase.
- Sales Pack: Adds products, quotes, invoices, purchases, subscriptions, inventory and payments for teams that quote and bill from the CRM.
- Other official integrations: VoIP, Google, Outlook, MailChimp, Zoom and Stripe integrations are available as official extensions.
- Cloud plans: EspoCRM Cloud costs 15 US dollars per user per month on Basic (minimum 3 users), 25 dollars on Enterprise (minimum 5 users) and 69 dollars on Ultimate (minimum 10 users), per the EspoCRM pricing page. Confirm current terms on that page before budgeting.
AGPL-3.0 is a copyleft license. If you modify EspoCRM and make it available to users over a network, the AGPL requires you to offer those users your modified source. Internal use without modification carries no source-release duty, but ask counsel to confirm how that applies to your custom code and extensions.
Krayin CRM is licensed under the MIT License, and its README states that the project will always be free under that license. The MIT License is permissive: you can use, modify, redistribute and sell software built on it, provided you keep the copyright and license notice. Krayin makes its money from paid extensions, hosting and services rather than from the core.
- Free core: The self-hosted CRM is free under MIT. Your costs are the server, the database, the PHP and Laravel stack, and the staff time to run it.
- Paid extensions: The README lists a Multi Tenant SaaS extension for several tenants on one instance with isolated data, a WhatsApp lead extension and a VoIP extension. Check each extension's terms and pricing before relying on it.
- Managed cloud hosting: Krayin advertises cloud hosting at 20 US dollars a month with unlimited users on its website. Confirm what the hosting plan covers, including backups, upgrades and data location.
- Support, custom development and migration: The website lists paid support and maintenance, custom development, white-label CRM, migration and integration services without published prices, so these require a written quote.
- Single sign-on: Neither the README nor the website documents SAML, OpenID Connect or LDAP for the core CRM. Any SSO work is an additional development or extension cost, so price it into the total.
MIT imposes few obligations beyond keeping the copyright and license notice, so you can modify Krayin and keep the changes private. That flexibility is an advantage for custom builds, but it also means the vendor's paid services, not the license, are where most of the spend sits. Ask for a written list of what each paid item includes before comparing totals.
What drives the running cost of each CRM
Running cost for a self-hosted CRM is mostly people time and infrastructure, plus any paid extensions or support you choose. The cards below separate what is paid once, such as the SSO build or the first install, from what recurs, such as hosting, upgrades, patching and per-user subscriptions. Use them to build the question list you send to each vendor and to DeployOpen before you ask for a written scope.
Infrastructure footprint
Krayin's README lists at least 3 GB of RAM along with PHP 8.3 or higher, Composer 2.5 or higher and MySQL 8.0.32 or higher or MariaDB 11.4 LTS or higher. EspoCRM's server configuration docs list PHP 8.3 to 8.5, MySQL 8.0 or newer, MariaDB 10.6 or newer or PostgreSQL 15, with cron or a scheduled task for background jobs, but they do not state a RAM minimum in the material supplied. Ask EspoCRM for its sizing guidance for your user count, then compare both against the instance size you would actually buy and the cost of running a staging copy.
Staff skills and hiring
Running Krayin means someone who can maintain a Laravel application, manage Composer dependencies and run php artisan tasks, while running EspoCRM leans on PHP and MySQL or MariaDB administration, cron jobs and web server configuration. Both are recurring payroll or contractor time. If your team already runs PHP and MySQL services, EspoCRM's skill profile is closer to what you have. If you need Laravel skills in-house, price that hire or contractor time into the three-year total before you commit.
Paid extensions and their renewals
EspoCRM's free core is AGPL-3.0, but reports, workflows and BPM sit in the paid Advanced Pack, and quotes, invoices and inventory sit in the Sales Pack. Krayin's core is MIT, while its Multi Tenant SaaS, WhatsApp and VoIP extensions are paid add-ons. Ask each vendor which features you need are free, whether extensions are one-time or subscription, how licenses are tied to an instance, and what happens to a feature when a license lapses or an upgrade changes its version.
SSO build effort
EspoCRM documents OpenID Connect sign-in since version 7.3, with optional user creation on first login and mapping of identity provider groups to teams. It also documents LDAP, including Active Directory and OpenLDAP. Krayin's README and website do not document SAML, OpenID Connect or LDAP sign-in for the core CRM, so single sign-on would need custom development or an extension. That build is a one-time cost, but its upkeep through every Krayin upgrade is recurring. Ask for the scope, test plan and ownership of the code in writing.
Support options and their cost
Krayin's website lists paid support and maintenance, custom development, white-label CRM, migration and integration services, all without published prices. EspoCRM's pricing page covers the cloud plans and the open-source download, and its support terms for self-hosted installs are not in the material supplied. Ask each vendor what response times, hours and channels are included, whether support is per incident or a monthly fee, and which items are excluded, such as security patches or version upgrades.
Upgrade effort over time
EspoCRM's current line is 10.0, with 10.0.10 released on October 14, 2026, and its previous major version, 9.0.0, arrived on January 20, 2025. Krayin's latest release is v2.2.7, released on October 16, 2026. Each upgrade needs a backup, a test run against your extensions and customizations and a rollback plan. The more custom code and paid add-ons you carry, the more each upgrade costs. Ask each vendor for its upgrade notes, deprecation policy and whether a retainer covers upgrades.
Per-user cloud pricing
EspoCRM Cloud is priced per user per month, at 15 US dollars on the Basic plan (minimum 3 users), 25 dollars on Enterprise (minimum 5 users) and 69 dollars on Ultimate (minimum 10 users), with the Advanced Pack included in all cloud plans. Krayin's cloud hosting is advertised at 20 US dollars a month with unlimited users. Multiply the per-user figure by your headcount for a year to compare fairly, then add any managed service or support costs that the flat price excludes. Ask whether the Krayin cloud price includes backups, upgrades and the Multi Tenant extension.
Moving data from EspoCRM to Krayin or the reverse
This sequence moves records, users and access rules from one CRM to the other without losing the business logic that sits around them. The output is a tested target instance, a signed-off mapping and a cutover date agreed with the people who use the system every day.
Inventory entities, fields and users
List every entity, custom field, layout, team, user and role in the source EspoCRM instance, and record which ones the business still uses. Export the field definitions and a sample of records so the mapping starts from what the system actually holds. Done when the team lead and a sales operations owner have signed off the inventory, with unused fields marked for retirement rather than migration.
Map entities and fields to the target
Build a field-by-field mapping from EspoCRM entities (accounts, contacts, leads, opportunities and any custom entities) to the matching Krayin objects, noting types that do not line up, such as multi-select values, relationships and date formats. Confirm with Krayin's maintainers or your DeployOpen engineer how custom fields are created and whether any entity has no direct equivalent. Done when every source field has a target, a transformation rule or a documented decision to drop it.
Map users, teams and permissions
Translate EspoCRM roles, teams and record-level access into Krayin's role-based access control, and identify any rule that depends on team hierarchy or field-level visibility that the target does not express the same way. Decide which accounts are re-created, which are linked to the identity provider later and which are retired. Done when a permission matrix lists each role on both sides, with gaps reviewed and accepted in writing.
Rebuild workflows and integrations on the target
Recreate EspoCRM workflows, business process rules, formula scripts, email templates and connectors on Krayin, either with its built-in features, custom development or a paid extension. Note that EspoCRM's Formula Script and Advanced Pack workflows will not transfer automatically, so each rule needs a written specification and a test case. Done when every automation in the inventory is marked as rebuilt, replaced or dropped, and each one has a documented owner.
Reconnect identity and sign-in
Rebuild single sign-on on the target, since EspoCRM's OpenID Connect and LDAP configuration will not carry over and Krayin's documentation does not describe SAML, OpenID Connect or LDAP sign-in for the core CRM. Confirm with Krayin whether an extension or custom development is needed, and plan a fallback login path for administrators. Done when a test user can sign in through the identity provider, group-based access behaves as the permission matrix requires, and the fallback path has been tried.
Import, reconcile and test
Run a trial import into a non-production instance using the target's import tooling, and compare record counts, relationships and sample values against the source export. EspoCRM's import documentation describes its own import behavior, which helps when you are checking the source side. Done when reconciliation reports show matching counts for each entity, and business users have tested their daily tasks, reports and approvals in the target.
Confirm vendor commitments before cutover
Before committing, ask EspoCRM and Krayin for written answers on license terms for any extensions you rely on, support windows for the release lines you will run, and the cost of paid services such as migration or custom development. Ask Krayin for a written quote covering its migration and integration services, since its website lists them without published prices. Done when the vendor answers and quotes are filed alongside the mapping, and any open gap has an owner.
Cut over and retire the source
Freeze edits in the source system, run the final delta import, switch users and integrations to the target, and keep the EspoCRM instance read-only for a period agreed in advance. Keep a verified backup of the source until the business confirms that nothing is missing. Done when users have signed in to the target, the post-cutover reconciliation matches, and the retirement plan for the source is approved.
Where EspoCRM and Krayin implementation projects usually run long
On EspoCRM, the long stretch is usually identity mapping and process design rather than installation. The OIDC docs describe optional user creation on first login, mapping of identity provider groups to EspoCRM teams, backchannel logout and a fallback login method, and EspoCRM's own 2FA is not compatible with OIDC. Each of those settings changes who can see which records, so the team has to decide which IdP groups map to which teams and roles, what the fallback login is for emergency access, and how service accounts that use API key or HMAC access are handled. Workflow and BPM design is the other slow area. Formula Script runs in before-save scripts, API before-save scripts, workflows and BPM, and the Advanced Pack provides the workflow and BPM tooling. A DeployOpen fixed-scope engagement would typically document the group-to-team map, the role matrix, each workflow's trigger and failure path, and the test cases used to sign off each change, so that later administrators can extend the rules without breaking access control.
On Krayin, the long stretch is usually the work the core does not include. Krayin's README and website do not document SAML, OpenID Connect or LDAP sign-in for the core CRM, so single sign-on has to be built through custom development or an extension, and that build needs its own design, testing and maintenance plan. Data migration is the second area to scope early: the team must map source fields to Krayin's custom fields, clean duplicate contacts and agree on the cutover window before any import runs. If the business needs the Multi Tenant SaaS extension or white-label work, tenant isolation, branding and per-tenant data rules become design decisions that affect every later change. Confirm with Krayin which extensions and services are available for your version, and ask for written acceptance criteria for each custom component. A DeployOpen fixed-scope engagement would plan these pieces as separate deliverables, with a documented SSO design, a migration runbook with reconciliation checks, and a record of every custom change for future upgrades.
Questions buyers ask before choosing EspoCRM or Krayin
What does it cost to self-host EspoCRM or Krayin?
Both cores are free to download and self-host, so the cost is the infrastructure, the people who run it and any paid add-ons. EspoCRM's open-source edition is AGPL-3.0 and free to self-host, according to the EspoCRM pricing page. Its paid extensions, such as the Advanced Pack for reports and workflows and the Sales Pack for quotes and invoices, are separate purchases. Krayin is MIT-licensed and its README says the project will always be free under that license, but its paid extensions, managed cloud hosting and support are priced separately. Drivers include server size, backup storage, staff time for upgrades and any custom development. Ask each vendor for the current price of every extension you need and for any license terms that apply per instance.
How long does an EspoCRM or Krayin deployment take?
The timeline depends mostly on scope, not on the software itself. A basic install of either core is a short technical task, but the work that takes time is configuration, data migration, identity integration, testing and user training. EspoCRM offers an installation script for Ubuntu, Debian and Linux Mint that deploys a Docker-based stack with Nginx and MariaDB, which can shorten the base setup, while a manual install on your own web server and database takes longer. Krayin installs with composer create-project followed by php artisan krayin-crm:install, or through its Docker setup. Neither source gives a deployment duration, so ask for a written plan with milestones before you commit.
What skills does the internal team need to run either CRM?
Both are PHP applications, so the team needs PHP operations skills, a web server such as Apache or Nginx, and database administration. EspoCRM requires PHP 8.3 to 8.5, MySQL 8.0 or newer, MariaDB 10.6 or newer, or PostgreSQL 15, plus cron or a scheduled task for background jobs. Krayin requires PHP 8.3 or higher, Composer 2.5 or higher, MySQL 8.0.32 or higher or MariaDB 11.4 LTS or higher, and at least 3 GB of RAM. Someone also has to own backups, patching, certificates and upgrades, which recur for the life of the system. Confirm with each vendor which versions remain supported at the time you deploy.
Can a small team run EspoCRM or Krayin without outside help?
A small team with PHP and Linux experience can usually run EspoCRM without outside help, because the core is mature, documented and includes an installation script with backup, restore and upgrade commands. Krayin is also manageable in-house, but its documented requirements and the absence of published enterprise identity features mean more of the integration work falls to your team. Outside help is most useful for identity integration, data migration from an existing CRM, custom development and hardening. DeployOpen plans, implements, integrates, hardens and documents self-hosted platforms in your own infrastructure under fixed-scope agreements, and offers retainers for ongoing upgrades. Decide based on the skills you have today and the work you need completed.
How is single sign-on added to Krayin?
Krayin's README and website do not document SAML, OpenID Connect or LDAP sign-in for the core CRM, so single sign-on has to be added through custom development or an extension. Confirm with the Krayin maintainers or Webkul whether an identity extension exists, what it supports and how it is licensed. Ask whether it covers group-to-role mapping and how sessions are revoked when a user leaves. By contrast, EspoCRM documents OpenID Connect sign-in since version 7.3, along with LDAP for Active Directory and OpenLDAP. Your own development team or an implementation partner would need to scope and test any Krayin SSO work before go-live.
How hard is it to switch from EspoCRM or Krayin later?
Switching is manageable if you keep data portable from the start. EspoCRM provides an import feature in its documentation, and both systems store standard relational data on MySQL, MariaDB or PostgreSQL, which makes export and transformation feasible. The main costs are mapping custom fields, workflows, users, permissions and attachments, plus retraining staff and rebuilding integrations. Krayin offers paid migration services, according to its website, but you should check whether those services cover the destination system you choose. Before you commit, ask each vendor for its data export format, a sample export, and a list of any proprietary features your processes depend on, such as Formula Script workflows in EspoCRM.
How DeployOpen helps choose, implement or migrate between these CRMs
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For EspoCRM vs Krayin CRM, that means starting from your team size, identity provider, database skills and extension needs, then agreeing the platform choice and the work in writing before any build begins.
How we scope
- Confirm which CRM functions your sales team needs, such as workflows, reports, custom fields and quoting.
- Map your identity provider needs, including whether OIDC or LDAP sign-in is required on day one.
- Agree in writing which extensions, integrations and hosting environment are in scope before work starts.
How we build
- Deploy the chosen CRM in your cloud account, data center or air-gapped network, on the supported PHP and database versions.
- Configure sign-in, roles and teams, and test that permissions behave as your sales structure requires.
- Where a feature is missing, scope custom development or extension work as a separate, written deliverable.
How we hand over
- Document the installation, configuration, backup and upgrade steps so your own staff can run the system.
- Walk through the data import, migration checks and rollback plan before switching users over.
- Deliver the configuration record and test results as written evidence for your internal reviews.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Plan upgrades against each platform's release cadence and support notes, which you should confirm with the vendor.
- Ask for a quote built from the written scope, since DeployOpen does not publish a price list.
