Fusion
Book a demo

Escape Salesforce. Own your data, your data model and your business logic.

We read your Salesforce org from its own metadata, with the Metadata API and the Tooling 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 org that we read from the metadata
Changes to your org
0
Changes that the analysis makes to your org
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 org describes the current system.

The metadata describes what your organisation built on Salesforce: the objects, the rules, the automation, the access and the screens. We read the metadata with the Metadata API and the Tooling API. The analysis does not change your org.

Show the platform:

Part of the system
SalesforceMetadata API · Tooling API
On Fusion
Data model
Objects, fields and picklists.CustomObject, CustomField, GlobalValueSet
A domain model, and a PostgreSQL schema built from it.
Business logic
Validation rules, formulas and Apex code.ValidationRule, ApexClass, ApexTrigger
Rules in code, each with its system tests.
Automation
Flows and approval processes.Flow, ApprovalProcess
Workflows, with schedules and retries in the application.
Access
Profiles, permission sets and sharing rules.Profile, PermissionSet, SharingRules
Roles and permissions, checked on each action, with an audit trail.
Screens
Page layouts, Lightning pages and list views.Layout, FlexiPage, ListView
Screens from the domain model, and custom screens where they matter.
Reports
Reports and dashboards.Report, Dashboard
Analytics on your own database.
Integrations
Named credentials and connected apps.NamedCredential, ConnectedApp
Integrations in the application, on the database that it already uses.
Records
Records and files.Bulk API 2.0, ContentVersion
Your records, in your own PostgreSQL database.

Each name in the table is the name that Salesforce documents. The analysis can reach only the parts that your integration user can see. The standard behaviour of Salesforce is not in the metadata, so the observation sessions show us that behaviour. The scope is the Salesforce core platform.

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

    Metadata API · Tooling 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 Salesforce 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

Salesforce is a trademark of its owner. Fusion has no affiliation with Salesforce.