Yes. Bulk user upload, current and in-flight claims migration, and configuration import (fee schedules, client lists, standard workflow rules) are all part of standard onboarding at no additional charge. Legacy closed claims that you want brought over for archive or historical reporting purposes are billed customer-by-customer based on volume and complexity. Complex migrations from another system — non-standard data formats, custom-field mapping, unusual integration requirements — are also scoped customer-by-customer at the demo. The standard pieces come over without extra cost; the unusual scope gets quoted up front so you know what you're paying before sign-up.

What's free as part of standard onboarding

The migration pieces every customer leaving another system actually needs are included:

Bulk user upload — your team's roster, role assignments, license tracking, branch assignments. We accept the export from your existing system and load it directly.
Current and in-flight claims migration — the claims you have in active workflow when you switch over. They come into FileTrac with their data, status, and history intact so your team picks up where they left off.
Configuration import — fee schedules, client lists, contract terms, standard workflow rules. The system-shaped pieces of your operation that determine how the platform behaves for you.

The principle is that the work most operations need to actually use FileTrac shouldn't have a separate price tag. You pay for the FileTrac subscription; standard onboarding is included.

What's billed customer-by-customer

Two scenarios get scoped individually rather than handled at flat rate:

Legacy closed claims. If you want every closed claim from the last decade brought over for archive, audit, or historical-reporting purposes — that's a different volume of data work than current/in-flight claims. The billing reflects the actual scope: how many years, how many records, what fields you need preserved, what document attachments come along. We scope this at the demo so you have the number before you sign.

Complex migrations. Some scenarios are not standard:

Non-standard data formats from a homegrown or unusual legacy system
Custom-field mapping where your existing fields don't have a FileTrac equivalent
Integration migrations where you're keeping a partner system on the other side of a bridge that needs to be reconfigured
Multi-tenant migrations where one source system is feeding multiple FileTrac instances

These get quoted individually because the work depends on what you actually have. If your situation looks like this, the demo is where the quote happens — same day usually, before you sign up.

What you bring to the migration

The faster you can hand over the inputs, the faster the migration completes:

From your existing claims system: export of users, current/in-flight claims (with their history, status, documents, and any associated financial records), client list, fee schedules, and the workflow configurations (status types, alert rules, document categories) you want preserved.
From your team: state licensing detail (relevant for the Personnel Manager), branch / location structure, the assignment rules you use to route claims, your standard letterhead and template letters.
From your accounting: if you're integrating with QuickBooks, NetSuite, or another accounting platform, the chart of accounts and any historical billing data you want carried forward.

ELIAS Concierge on the website can answer questions about input requirements before you sign up. ELIAS AI in the dashboard answers questions about the migration once you're in.

How the migration runs in parallel with going live

The migration doesn't block you from running real claims. Most customers start running claims for their first client (with the configuration done for that client) within hours of sign-up. The migration of historical data and additional clients runs in parallel during the first few weeks of operation. You're not in a "training-only" phase while data loads — you're operating live.

This matches the phased per-client onboarding pattern (set up first client, run real claims, add the next client, repeat). The migration follows the same rhythm.

What ELIAS AI does in the migration today — and what it doesn't

ELIAS AI today acts as a knowledge source during the migration. Ask it where to put a specific field, how a status type maps from your old system to FileTrac, what the default fee schedule structure looks like — and it points you to the right setting and explains the answer.

ELIAS AI does not yet automate the migration itself. Action-taking capabilities — building configurations from your existing system's exports, mapping fields automatically, generating the workflow rules from your contract documents — are in active development and ship weekly. For migrations happening today, the configuration work is done by the customer (with ELIAS AI guiding) or by the implementation team at the Business or Enterprise support tiers.

What changes by support tier

The support plan you select shapes how much hands-on migration help you get:

Basic Support (Grow, Build, Adapt, Sustain). Self-serve migration with ELIAS AI as a Q&A guide and the documentation. Standard onboarding pieces are still free; you do the import work yourself with our guidance.
Business Support (Business, Business Plus). Implementation-team time during onboarding for configuration and migration work. Per-line-item rates apply for any custom development on top of the standard import.
Enterprise Support (Enterprise, Enterprise Plus). Implementation-team time with design fees included. Lower flat fees on custom work, 10 hours of training annually, on-site training available.

The published rates for custom development, custom reports, and training are on the pricing page.

Can I migrate my existing claim data into FileTrac, and how?