Fusion
Book a demo

Escape Dynamics 365. Own your data, your data model and your business logic.

We read your Dynamics 365 environment from its own metadata, with the Dataverse Web API, and we watch the people who use it. Then we rebuild the system on Fusion, on the hosting that you choose. In the same work, we fix the pain points, rewrite the documentation and the user guides, and close the compliance gaps.

Book the one-hour session See what we read
Parts that we read
8
Parts of your environment that we read from the metadata
Changes to your environment
0
Changes that the analysis makes to your environment
Problem & Opportunity Statement session
1h
A Problem & Opportunity Statement session with your sponsor
Seat licences on the new system
0
Seat licences for the people who use the new system

What we read

The metadata in your environment describes the current system.

The metadata describes what your organisation built on Dynamics 365: the tables, the rules, the automation, the access and the screens. We read the metadata with the Dataverse Web API. The analysis does not change your environment.

Show the platform:

Part of the system
Dynamics 365Dataverse Web API
On Fusion
Data model
Tables, columns and relationships.EntityDefinitions, Attributes, RelationshipDefinitions
A domain model, and a PostgreSQL schema built from it.
Business logic
Business rules and plug-ins.workflow, sdkmessageprocessingstep
Rules in code, each with its system tests.
Automation
Cloud flows in solutions, and classic workflows.workflow
Workflows, with schedules and retries in the application.
Access
Security roles, teams and field security.role, team, fieldsecurityprofile
Roles and permissions, checked on each action, with an audit trail.
Screens
Forms, views and model-driven apps.systemform, savedquery, appmodule
Screens from the domain model, and custom screens where they matter.
Reports
Charts and dashboards.savedqueryvisualization, systemform
Analytics on your own database.
Integrations
Service endpoints and connection references.serviceendpoint, connectionreference
Integrations in the application, on the database that it already uses.
Records
Records, notes and files.Web API, annotation
Your records, in your own PostgreSQL database.

Each name in the table is the name that Microsoft documents. The analysis can reach only the parts that your integration user can see. The standard behaviour of Dynamics 365 is not in the metadata, so the observation sessions show us that behaviour. The scope is Dynamics 365 applications on Dataverse.

The method

Hours of your people's time, not weeks of workshops.

Three of the six steps need people from the business. The metadata analysis is step 03, and it runs without them.

  1. 01

    Problem & Opportunity Statement session

    1 hour · Business time

  2. 02

    Observation sessions

    1–2 hours each · Business time

  3. 03

    Metadata analysis

    Dataverse Web API

  4. 04

    Domain model and design

  5. 05

    Build, test and document

    Business time

  6. 06

    Data migration and switch-over

Read each step See the four results

Bring the Dynamics 365 system that you most want to leave.

One hour with your sponsor starts the work. Bring the problem that your current system does not solve today.

Book the one-hour session Start with Idea to Impact

Microsoft Dynamics 365 is a trademark of its owner. Fusion has no affiliation with Microsoft.