Skip to main content

Fusion — XactAnalysis to FileTrac Legacy Default Mapping

Coming Soon — Fusion is in development and not yet available in production.

Status: Shipping June 2026

Fusion is currently in development and scheduled for release in June 2026. The information in this article reflects the planned design. Features and interface details may change before launch.

What Is the Default Mapping?

Fusion ships with a pre-configured mapping template that connects XactAnalysis (XA) fields to their corresponding FileTrac Legacy fields. This XA to FileTrac Legacy Default Mapping provides a ready-to-use baseline so that organizations using both systems can begin exchanging data immediately without building every transformation from scratch.

The default mapping covers the most common claim data fields — including claim identifiers, insured information, loss details, status codes, financial totals, and adjuster assignments — and includes the lookup tables needed to translate XA-specific values into FileTrac equivalents.

Immutable Baseline

The default mapping is immutable. It cannot be edited, renamed, or deleted. This design decision ensures that every FileTrac Evolve installation always has a known-good reference configuration available, regardless of what custom mappings have been created.

Why Immutability Matters

Integration configurations can be fragile. A single incorrect field mapping or a deleted lookup entry can cause data corruption, duplicate records, or silent data loss. By making the default mapping read-only, Fusion guarantees that:

  • Administrators can always compare their custom work against the original template.

  • A working configuration is available for rollback if a custom mapping produces unexpected results.

  • New team members can study the default mapping to understand the intended data flow before making changes.

Working with the Default Mapping

Viewing

Open the default mapping from the Fusion main screen. The Transformation Editor displays all field-level rules in the standard card-based view. You can expand any card to see the full transformation detail, including source field, destination field, transformation type, and assigned lookup table.

Because the mapping is immutable, all editing controls are disabled. The side panel opens in read-only mode when you select a card.

Copying to Create a Custom Mapping

To modify the XA-to-FileTrac configuration for your organization's specific needs, create a copy of the default mapping. The copy is fully editable — you can add, remove, or modify transformations and lookups without affecting the original baseline.

This pattern (immutable default plus editable copy) follows the same approach used by many enterprise systems: a vendor-provided template that can be forked but never altered, ensuring a safe rollback path is always available.

Comparing Custom to Default

Fusion's compare view allows you to place a custom mapping side by side with the default to see exactly what has changed. Added, removed, and modified transformations are highlighted, making it easy to audit the differences before deploying a custom configuration to production.

Covered Field Categories

The default mapping includes transformations for the following XactAnalysis-to-FileTrac field categories:

Category

Examples

Claim Identification

Claim number, XA reference ID, file number

Insured Information

Name, address, contact details

Loss Details

Date of loss, cause of loss, loss description

Status

Claim status, assignment status, completion status

Financial

Reserve amounts, payment totals, deductible

Adjuster Assignment

Assigned adjuster, assignment date, priority

Dates

Reported date, inspection date, close date

Each category may contain multiple individual field-level transformations. The exact field list will be documented in the Fusion release notes at launch.

Extending Beyond XactAnalysis

The XA-to-FileTrac-Legacy template is the first default mapping provided with Fusion. Additional default mappings for other integration partners (such as Symbility) may be added in future releases. Organizations can also build entirely custom mappings for any external system by starting from a blank configuration using the Fusion Wizard.

Did this answer your question?