Migrate from Exxas Cloud Business Platform to Microsoft Dynamics 365 Business Central

Exxas Central module holds both person-level contacts and organizational company records in a single unified model. We split these into the destination's separate Contact (person) and Account or Customer (organization) objects. The Exxas contact's associated company reference becomes the AccountId or Customer Number lookup in Dynamics. German-language field labels (Firmenname, Vorname, Nachname, Strasse, PLZ, Ort) are translated to English equivalents during preprocessing before field mapping. Custom fields attached to Exxas contact or company records migrate as custom fields on the destination Contact and Account or Customer entities.

Exxas Sales deals map to Dynamics 365 Opportunity records or Business Central sales documents depending on the destination edition. HubSpot Deal pipeline and stage names (in German) translate to English StageName values. Deal amount fields migrate as estimatedvalue with currency resolved from the Exxas multi-currency configuration. Closed-won and closed-lost dates migrate; Exxas custom deal fields migrate as custom Opportunity fields.

Exxas Sales pipelines with configurable stages become Dynamics 365 Record Types with corresponding Sales Processes. Each Exxas pipeline maps to one Record Type; Exxas stage names become StageName picklist values with probability percentages migrated to stageprobability. Stage ordering is preserved; custom stage properties are flagged for manual post-migration review.

Exxas Service tickets map to Dynamics 365 Customer Service cases. Ticket status, priority, and assignment relationships preserve; the linked shared mailbox reference maps to a queue or user assignment in Dynamics. German-language ticket subject and description fields migrate as English text. Attachment handling depends on destination attachment storage configuration; we migrate file references and flag any attachments requiring manual relinking.

Exxas project hierarchies map to Dynamics 365 Project Operations projects or Business Central jobs. Tasks and sub-tasks migrate as project tasks with hierarchy preserved. Exxas sprint assignments (Kanban boards) do not have a direct Dynamics equivalent; we migrate the task list and sprint membership is flagged for manual recreation in Dynamics Project Boards or a Project for Operations board. Time entries migrate as project time entries linked to the assigned employee resource. Exxas project billing milestones map to project contract lines.

Exxas product records with pricing tiers and stock-on-hand migrate to Dynamics 365 Released Products (Finance and Operations) or Items (Business Central). Exxas pricing tiers map to price groups and sales prices on the destination product. Stock-on-hand values migrate to inventory dimensions (site, warehouse, location) but Exxas warehouse-specific bin locations require manual reconciliation because bin-level data may not map to a 1:1 warehouse structure in Dynamics.

Exxas employee profiles with job titles and current assignments map to Dynamics 365 Human Resources worker records. Effective-dated HR entries migrate with the valid-from and valid-to dates preserved as employment effective dates. Compensation history with pay grades and salary amounts migrates to the worker's compensation history entity. Country-specific benefit assignments are flagged for manual review because Exxas benefit configurations are Swiss-specific.

Exxas Finance chart of accounts migrates to Dynamics 365 main accounts. Account number, name, account type, and dimension structure preserve. German-language account names translate to English during preprocessing. Exxas cost center and department dimensions map to Dynamics 365 Financial Dimensions. Account valid-from and valid-to dates for historical accounts migrate as posting definitions allow.

Exxas open AP and AR records migrate as open vendor invoices and customer invoices in Dynamics 365 Finance or as open ledger entries in Business Central. Invoice amounts, due dates, and currency codes preserve. Exxas payment terms map to Dynamics payment term codes. Historical closed periods export as read-only reference files because Dynamics does not overwrite closed accounting periods; the customer's admin reviews and posts any adjustments manually.

Exxas general journal entries migrate to Dynamics 365 general journal lines. Journal batch name, posting date, account, dimension, debit amount, credit amount, and description preserve. We migrate the current and prior year open journal entries; deeply historical closed periods are exported as read-only archive files. Journal entry approval workflows in Exxas do not migrate; we document the approval structure for the admin to rebuild in Dynamics approval workflows.

Exxas custom data masks with individual fields per entity category are extracted as field definitions and values. We map each Exxas custom field to a typed Dynamics 365 custom field (text, number, date, picklist, lookup) on the equivalent standard entity. Field-level security, validation rules, and business rules referencing custom fields are flagged for the customer's Dynamics admin to configure after migration. Exxas data mask layouts do not map to Dynamics 365 form design.

Exxas user records (owners assigned to records across modules) map to Dynamics 365 User accounts. We resolve users by email match against the destination tenant. Any Exxas owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. User security roles and Exxas concurrent-user slot assignments do not map to Dynamics 365 security roles automatically; we document the role requirements for manual assignment.

Exxas marketing campaigns with lead flow stages migrate to Dynamics 365 Marketing campaigns and leads if the destination subscription includes the Dynamics 365 Marketing app. Campaign name, status, type, and target audience criteria preserve. Exxas lead scoring and grading values migrate to a custom lead score field. Automated lead nurture flows in Exxas do not migrate; we deliver a campaign and lead flow inventory document for the admin to rebuild in Dynamics 365 Marketing or a third-party marketing automation tool.

Exxas customer portal-facing records (invoices, orders, support tickets, asset records) migrate as linked records on the customer or contact account. Portal configuration (branding, page layouts, permission sets) does not migrate because Exxas portal settings are platform-specific. We deliver a portal feature inventory with a recommendation for Dynamics 365 Customer Self-Service Portal or an Experience Cloud portal as the replacement.