Fusion

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

We read your ServiceNow instance from its own metadata, with the Table 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.

Parts that we read
8
Parts of your instance that we read from the metadata
Changes to your instance
0
Changes that the analysis makes to your instance
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 instance describes the current system.

The metadata describes what your organisation built on ServiceNow: the tables, the rules, the automation, the access and the screens. We read the metadata with the Table API. The analysis does not change your instance.

Show the platform:

Part of the system
ServiceNowTable API
On Fusion
Data model
Tables, columns and choices.sys_db_object, sys_dictionary, sys_choice
A domain model, and a PostgreSQL schema built from it.
Business logic
Business rules and script includes.sys_script, sys_script_include
Rules in code, each with its system tests.
Automation
Flows and workflows.sys_hub_flow, wf_workflow
Workflows, with schedules and retries in the application.
Access
Roles, groups and access control rules.sys_user_role, sys_user_group, sys_security_acl
Roles and permissions, checked on each action, with an audit trail.
Screens
Forms, lists and UI actions.sys_ui_form, sys_ui_list, sys_ui_action
Screens from the domain model, and custom screens where they matter.
Reports
Reports.sys_report
Analytics on your own database.
Integrations
REST messages and transform maps.sys_rest_message, sys_transform_map
Integrations in the application, on the database that it already uses.
Records
Records and attachments.Table API, sys_attachment
Your records, in your own PostgreSQL database.

Each name in the table is the name that ServiceNow documents. The analysis can reach only the parts that your integration user can see. The standard behaviour of ServiceNow is not in the metadata, so the observation sessions show us that behaviour. The scope is ServiceNow applications on the Now 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

    Table API

  4. 04

    Domain model and design

  5. 05

    Build, test and document

    Business time

  6. 06

    Data migration and switch-over

Bring the ServiceNow 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.

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