Migrate your Exxas Cloud Business Platform data
Swiss all-in-one cloud ERP+CRM built for SMEs, covering eight integrated functional areas from sales through accounting. Exxas targets German-speaking mid-market companies that need a single platform instead of stitched-together point solutions.
In its favor
Why people choose Exxas Cloud Business Platform
The signal that keeps Exxas Cloud Business Platform on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Customers choose Exxas because it replaces multiple separate tools with one integrated platform, eliminating data silos between CRM, ERP, and project management.
The concurrent-user licensing model reduces cost for part-time or occasional users, as companies pay for simultaneous sessions rather than named seats.
Industry-specific vertical solutions for agencies, law firms, IT service providers, and trading companies reduce configuration time for those sectors.
The platform is built and operated by a Swiss vendor, which appeals to companies with data residency or compliance requirements in Switzerland or Germany.
Exxas own development team uses the platform to run its product management and engineering, meaning features are tested against real operational use cases.
The platform is German-language only, which becomes a blocker when companies grow internationally or hire English-speaking staff.
Organizations that have outgrown mid-market ERP complexity report that Exxas lacks the depth needed for multi-entity accounting, inter-company eliminations, or advanced financial consolidation.
Companies moving to or from the platform cite difficulty extracting complete data exports, as the API requires authentication and Swagger documentation is not publicly accessible without a login.
Reasons to switch
Why people leave Exxas Cloud Business Platform
The recurring reasons buyers give for replacing Exxas Cloud Business Platform. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Exxas Cloud Business Platform fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Exxas Cloud Business Platform pricing overview
Exxas publishes pricing only on request and does not disclose tier prices on its website. The platform uses a concurrent-user licensing model, where each subscription slot allows one simultaneous user regardless of the total number of named users in the organization. This model benefits companies with many part-time or occasional users.
Startup
Tier 1 of 3
Not publicly published
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Exxas Cloud Business Platform's schedule — see our quote-based pricing →
What gets migrated
Exxas Cloud Business Platform object support
Object-by-object support for Exxas Cloud Business Platform migrations. Per-pair details surface during scoping.
Contacts and Companies
Mapping requiredThe Central module holds both person-level contacts and organizational company records. We map these to the destination's equivalent Account or Contact objects, preserving any custom fields and the link between a contact and its parent company.
Sales Pipelines and Stages
Mapping requiredThe Sales module uses a pipeline metaphor with configurable stages and deal records. We migrate stage names as-is and flag any custom stage properties for manual post-migration review.
Service Tickets
Mapping requiredThe Service module manages tickets, linked to shared mailboxes and customer assets. We preserve ticket status, priority, and assignment relationships, but attachment handling depends on destination storage limits.
Projects and Sprints
Mapping requiredProjects in Exxas contain tasks, sprints, Kanban boards, and time entries. We map the project hierarchy and linked employee assignments, but sprint burndown metrics are recalculated post-migration on the destination side.
Products and Inventory
Mapping requiredProducts carry pricing, stock levels, and BOM relationships. We transfer product records with pricing tiers and stock-on-hand, but warehouse-specific bin locations require manual reconciliation.
Employees and HR Records
Mapping requiredThe Human Resources module holds employee profiles, job titles, and compensation history with effective dates. We preserve historical pay data and current assignments, flagging any country-specific benefit records for HR review.
Payroll History
Not in this platformExxas payroll runs are tightly coupled to Swiss social security and tax calculation engines. We do not migrate payroll run data directly; instead we export employee compensation rates and historical earnings summaries for manual re-entry on the destination payroll system.
Finance Journals and Accounts
Mapping requiredThe Finance module contains chart of accounts, open AP/AR records, and journal entries. We migrate the account structure and current open items, but historical closed periods are exported as read-only summaries rather than re-posted transactions.
Custom Data Masks and Fields
Mapping requiredExxas allows custom data masks with individual fields per asset or entity category. We extract all custom field definitions and values, mapping them to the destination's custom field infrastructure or storing them as structured JSON payloads.
Customer Portal Data
Mapping requiredThe Personal Customer Portal grants clients access to invoices, orders, support tickets, and asset records. We migrate portal-facing records that belong to the customer relationship, but portal configuration and branding settings require manual re-setup.
| Object | Support | Notes |
|---|---|---|
| Contacts and Companies | Mapping required | The Central module holds both person-level contacts and organizational company records. We map these to the destination's equivalent Account or Contact objects, preserving any custom fields and the link between a contact and its parent company. |
| Sales Pipelines and Stages | Mapping required | The Sales module uses a pipeline metaphor with configurable stages and deal records. We migrate stage names as-is and flag any custom stage properties for manual post-migration review. |
| Service Tickets | Mapping required | The Service module manages tickets, linked to shared mailboxes and customer assets. We preserve ticket status, priority, and assignment relationships, but attachment handling depends on destination storage limits. |
| Projects and Sprints | Mapping required | Projects in Exxas contain tasks, sprints, Kanban boards, and time entries. We map the project hierarchy and linked employee assignments, but sprint burndown metrics are recalculated post-migration on the destination side. |
| Products and Inventory | Mapping required | Products carry pricing, stock levels, and BOM relationships. We transfer product records with pricing tiers and stock-on-hand, but warehouse-specific bin locations require manual reconciliation. |
| Employees and HR Records | Mapping required | The Human Resources module holds employee profiles, job titles, and compensation history with effective dates. We preserve historical pay data and current assignments, flagging any country-specific benefit records for HR review. |
| Payroll History | Not in this platform | Exxas payroll runs are tightly coupled to Swiss social security and tax calculation engines. We do not migrate payroll run data directly; instead we export employee compensation rates and historical earnings summaries for manual re-entry on the destination payroll system. |
| Finance Journals and Accounts | Mapping required | The Finance module contains chart of accounts, open AP/AR records, and journal entries. We migrate the account structure and current open items, but historical closed periods are exported as read-only summaries rather than re-posted transactions. |
| Custom Data Masks and Fields | Mapping required | Exxas allows custom data masks with individual fields per asset or entity category. We extract all custom field definitions and values, mapping them to the destination's custom field infrastructure or storing them as structured JSON payloads. |
| Customer Portal Data | Mapping required | The Personal Customer Portal grants clients access to invoices, orders, support tickets, and asset records. We migrate portal-facing records that belong to the customer relationship, but portal configuration and branding settings require manual re-setup. |
Gotchas
What to watch for in Exxas Cloud Business Platform migrations
Issues we've hit on past Exxas Cloud Business Platform migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API 2.0 Swagger documentation requires authentication
German-language only interface with no English localization
Concurrent-user licensing means simultaneous session limits matter
| Severity | Issue |
|---|---|
| Medium | API 2.0 Swagger documentation requires authentication |
| Medium | German-language only interface with no English localization |
| Low | Concurrent-user licensing means simultaneous session limits matter |
Leaving Exxas Cloud Business Platform?
Where Exxas Cloud Business Platform customers move next
6 destinations Exxas Cloud Business Platform can migrate to.
How a Exxas Cloud Business Platform migration works
Four steps, Exxas Cloud Business Platform-specific
Connect
OAuth 2.0 (Exxas credentials via api.exxas.net portal) into Exxas Cloud Business Platform. Scopes limited to read-only on the data we move.
Map
We translate Exxas Cloud Business Platform-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Exxas Cloud Business Platform quirks before production.
Migrate
Full migration with Exxas Cloud Business Platform rate-limit handling. Rollback available throughout.
FAQ
Exxas Cloud Business Platform migration FAQ
Answers to the questions buyers ask most during Exxas Cloud Business Platform migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Exxas Cloud Business Platform migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Exxas Cloud Business Platform.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Exxas Cloud Business Platform setup and destination — written quote back within a business day.