Brilliance One Tools

Move the data. Keep the operation controlled.

Import, export, map, validate, review, clean, migrate, and manage business data across Brilliance One with administrative workflows designed for controlled data operations.

Brilliance One Tools gives authorized administrators a shared place to move and maintain operational information while preserving permissions, validation, review, security, and available activity history across the broader Business Operating System.

Explore Tools View Data Capabilities
Import • Export • Map • Validate • Govern
Brilliance One business data import export migration validation and administration tools

Data Operations

Manage business data without treating every change like a development project.

Use structured administrative tools to move, map, validate, review, export, correct, and maintain supported operational data while keeping higher-impact actions appropriately restricted.

Move

Import & Export

Move supported data into or out of Brilliance One for migration, onboarding, reporting, analysis, archival, integration, and other approved business purposes.

Verify

Mapping & Validation

Review source fields, destination fields, required values, formats, classifications, and other detectable issues before supported data is committed.

Govern

Controlled Administration

Use platform permissions, security controls, administrative access, review, and available logging around data operations that can affect large portions of the business.

Beyond File Upload

Moving the file is easy. Moving the business data correctly is harder.

A successful upload does not automatically mean the information belongs in the right field, matches the destination model, preserves relationships, or is appropriate to commit.

  • What records are being moved?
  • Where should each field go?
  • Which values are required?
  • Which formats are valid?
  • Which relationships must be preserved?
  • Should records be created or updated?
  • Who is authorized to perform the operation?
  • What errors require review?
  • What happened during the migration?
  • How will the resulting data be maintained afterward?

Governed Data Operations

Data movement should be deliberate.

Brilliance One Tools is designed to put mapping, validation, review, permissions, import or export activity, and ongoing data maintenance around major administrative data operations.

The goal is not simply to move records. It is to move useful information into the operational structure responsible for using it.

Tools Capabilities

Import it. Validate it. Review it. Manage it.

Brilliance One Tools supports common data-administration requirements across the platform while keeping those workflows connected to the modules and security model they affect.

Import

Bulk Data Intake

Bring supported legacy, external, onboarding, or bulk operational information into Brilliance One using structured import workflows.

Mapping

Source → Destination

Associate incoming columns and values with the appropriate supported Brilliance One fields before committing records.

Validation

Data Quality Checks

Identify supported missing fields, invalid formats, unexpected values, incomplete mappings, and other detectable structural issues.

Review

Administrative Verification

Give authorized administrators an opportunity to review supported mappings, issues, and incoming records before committing significant changes.

Export

Structured Data Output

Export supported business information for reporting, authorized analysis, migration, archival, external processing, or other approved uses.

Cleanup

Ongoing Data Maintenance

Support recurring administrative cleanup, classification, validation, correction, and data-management work after migration is complete.

Migration

System Transition

Use templates, field mapping, validation, and controlled bulk processes to reduce friction when moving supported records from another system.

Security

Permission-Aware Operations

Restrict supported data-management functions to authorized administrators using the broader Brilliance One identity and permission model.

History

Administrative Traceability

Maintain available information around supported imports, exports, uploads, mappings, and other significant administrative data activity.

Data Import

Bring data in with structure and context.

Import workflows help move supported information from legacy systems, spreadsheets, external applications, onboarding files, and bulk administrative sources into Brilliance One.

  • Structured import templates
  • Field mapping
  • Required-field checks
  • Format validation
  • Value review
  • Bulk records
  • Destination selection
  • Create or update behavior where supported
  • Administrative review
  • Import history

Migration Support

Legacy data should not have to stay trapped in the legacy system.

Structured import, mapping, and validation can reduce the amount of custom development required for common onboarding and migration workflows.

More complicated migrations may still require specialized transformation or development when the source data does not align cleanly with the destination model.

Import Workflow

Prepare. Map. Validate. Commit.

A structured migration process separates preparation from production changes so obvious issues can be reviewed before supported records become operational data.

1

Prepare

Gather the appropriate source data, use the expected structure, identify destination modules, and clean obvious issues in the source where practical.

2

Map & Validate

Associate source values with supported destination fields and review required fields, formats, classifications, relationships, and detectable validation issues.

3

Review & Commit

Review the prepared operation and move approved records into Brilliance One using the supported import process.

Field Mapping

Make sure the source field means the same thing at the destination.

Field names alone do not guarantee that two systems define information the same way. Mapping gives administrators a controlled place to determine where supported incoming values belong.

  • Source columns
  • Destination fields
  • Required fields
  • Identifiers
  • Statuses
  • Classifications
  • Dates
  • Amounts
  • Relationship fields
  • Unmapped values

Semantic Mapping

“Status” in one system may not mean “Status” in another.

Mapping is more than matching column names. Administrators may need to understand what the source value represents and whether the destination expects the same business meaning.

The goal is not simply to fill fields. It is to preserve usable business information.

Data Validation

Catch common problems before they become operational problems.

Validation cannot prove that every incoming value is factually correct, but it can identify supported structural and formatting problems before data is committed.

Missing Values

Identify supported required destination fields that are missing expected information.

Invalid Formats

Detect supported values that do not match the structure expected by the destination.

Mapping Problems

Identify source fields that have not been associated with an appropriate destination.

Unexpected Values

Review values that do not align with supported classifications, options, types, or configured expectations.

Relationship Problems

Review supported identifiers or relationships that cannot be resolved to the expected destination record.

Administrator Review

Give authorized users an opportunity to inspect detected issues before proceeding with significant data movement.

Data Quality

Valid data is not necessarily correct data.

Automated validation can identify structural issues, but the organization remains responsible for whether the underlying source information accurately represents the customer, product, transaction, employee, asset, or business activity involved.

  • Structure can be validated
  • Formats can be checked
  • Required values can be identified
  • Classifications can be compared
  • Mappings can be reviewed
  • Business meaning still requires judgment
  • Source quality still matters
  • Administrative review still matters

Human Review

Software can recognize an email address. It cannot always know whether it belongs to the right customer.

Data quality combines technical validation with business understanding.

Brilliance One Tools can help identify detectable problems while leaving business-specific judgment with the people who understand the data.

Record Matching

Importing a record should not automatically mean creating another copy.

Where supported, identifiers and matching rules can help determine whether incoming information should create a new record, update an existing record, or require administrator review.

Identify

Matching Information

Use supported identifiers or matching information appropriate to the destination object and workflow.

Decide

Create or Update

Apply supported create, update, or review behavior according to the configured import workflow.

Review

Ambiguous Matches

Route uncertain or conflicting information through appropriate administrative review instead of assuming every potential match is correct.

Related Records

Moving records is not enough when the relationships matter too.

Business data frequently depends on relationships between customers, contacts, products, invoices, projects, documents, employees, assets, vendors, and other records.

  • Company → Contact
  • Customer → Address
  • Invoice → Customer
  • Invoice → Products
  • Project → Customer
  • Project → Employees
  • Asset → Employee
  • Asset → Vendor
  • Document → Business Record
  • Other supported relationships

Connected Data

A perfectly imported invoice is still incomplete if it loses the customer it belongs to.

Migrations should preserve the useful relationships between records where the supported data and destination model allow them to be reconstructed.

That is especially important in a Business Operating System where operational context is created through connected records.

Data Export

Take authorized data where the business needs it.

Export supported business information for reporting, authorized analysis, migration, archival processes, external processing, audit support, or other approved operational uses.

  • Field selection
  • Filtering
  • Structured output
  • Module-specific exports
  • Reporting extracts
  • Migration data
  • Authorized analysis
  • Administrative review
  • Export history

Controlled Export

The ability to view a record should not automatically imply permission to export the database.

Large exports can increase the sensitivity and portability of business information.

Supported export functions should remain subject to the organization's access model, administrative responsibility, and data-handling policies.

Cross-Module Data

One administrative toolset across the operating system.

Supported data-management workflows can operate across multiple Brilliance One business areas instead of requiring every module to invent another migration and export process.

CRM

Accounts, Contacts & Leads

Import or export supported customer, organization, lead, contact, address, classification, and relationship information.

Products

Products & Inventory

Move supported catalog, product, inventory, classification, pricing, identifier, and related operational information where available.

Accounting

Financial Records

Work with supported invoices, vendors, financial records, transactions, classifications, and other accounting information where the workflow allows it.

Projects

Delivery Data

Use supported project, task, status, customer, assignment, time, and other operational data in migration and administrative workflows.

Human Resources

Workforce Records

Move supported employee, organizational, training, workforce, and related HR information through appropriately restricted workflows.

Technology

Asset Information

Import or export supported asset, assignment, vendor, maintenance, warranty, and lifecycle information where available.

Documents

Files & Metadata

Manage supported document and file movement as part of approved migration, import, export, and administrative processes.

Firearms

Specialized Records

Use only supported and appropriately controlled migration or administrative workflows for specialized firearms information where enabled.

Other Modules

Connected Operations

Extend common import, export, validation, and administrative patterns to additional supported Brilliance One operational areas.

Data Maintenance

Data management does not end after migration.

Even clean migration data can become inconsistent as employees, customers, products, projects, classifications, and business processes change over time.

  • Validation workflows
  • Administrative cleanup
  • Record correction
  • Classification maintenance
  • Mapping review
  • Import troubleshooting
  • Export preparation
  • Operational data maintenance

Ongoing Data Quality

A migration creates the starting point. Operations determine what happens next.

Brilliance One Tools gives authorized administrators a place for recurring data-management work rather than treating data quality as a one-time onboarding project.

Maintaining useful business information is an ongoing operational responsibility.

System Migration

Moving platforms should not require starting the business over.

Native templates, mapping, validation, bulk imports, review, and cross-module data workflows can reduce migration friction when moving supported operational information into Brilliance One.

1

Extract

Export appropriate customer, operational, product, financial, project, workforce, or other records from the source system using the data available there.

2

Transform

Prepare the data for Brilliance One by cleaning obvious problems, mapping fields, converting classifications where needed, and validating supported values.

3

Load & Review

Import approved records into the appropriate modules and review the resulting information before depending on it for broader business operations.

Migration Reality

Not every migration is just a CSV upload.

Older systems can contain custom fields, proprietary relationships, duplicated information, inconsistent classifications, inaccessible history, attachments, notes, unsupported formats, or data models that do not have a direct equivalent.

  • Custom fields
  • Different identifiers
  • Legacy classifications
  • Duplicate records
  • Missing relationships
  • Embedded notes
  • Attachments
  • Historical activity
  • Unsupported source formats
  • Business-specific transformations

Standard + Specialized Migration

Use native tools for common migrations. Use engineering when the source system requires it.

Tools should reduce unnecessary custom migration work without pretending every legacy system can be converted safely through the same universal import template.

Complex migrations may require API integration, transformation logic, data analysis, or specialized migration support.

Sensitive Data Movement

Imports and exports can increase security risk.

Administrative data tools can expose large amounts of customer, employee, financial, operational, document, or industry information at once. Access should reflect that impact.

  • Administrative permissions
  • Role-based access
  • Security groups
  • Module access
  • Export authorization
  • Protected file handling
  • Secure transport
  • Sensitive-data protection
  • Activity logging
  • Data-handling procedures

Data Portability

A bulk export can turn thousands of protected records into one portable file.

That makes export privileges materially different from ordinary record viewing.

Organizations should limit high-impact data-movement capabilities to authorized users and establish procedures for protecting exported information after it leaves the platform.

Activity History

Major data operations should leave useful context.

Available administrative and operational history can help explain when supported imports, exports, uploads, mappings, or significant data changes occurred.

  • Import activity
  • Export activity
  • File uploads
  • Mapping changes
  • Administrative updates
  • Sensitive operations
  • User context
  • Recorded timestamps
  • Status information
  • Error context where available

Traceability

“The data changed” should not be the end of the investigation.

Activity history can give administrators useful context when troubleshooting migration issues, reviewing significant changes, investigating unusual behavior, or understanding when major data operations occurred.

Error Handling

A failed record should explain what needs attention.

Where supported, import results and validation feedback should help administrators distinguish successful records from records requiring additional correction or review.

Detect

Validation Issues

Identify supported problems before or during processing when destination requirements cannot be satisfied.

Explain

Error Context

Provide available information describing which record, mapping, field, or value requires administrative attention.

Correct

Review & Retry

Correct source or mapping problems and repeat the appropriate supported operation when the data is ready.

Data Portability

Operational data should remain usable beyond one screen.

Authorized exports and APIs provide pathways for organizations to use supported Brilliance One information in reporting, integrations, migration, archival, analysis, and other legitimate business workflows.

  • Authorized exports
  • Reporting extracts
  • API access where supported
  • Migration workflows
  • External analysis
  • Archival processes
  • Integration use cases
  • Business continuity planning

Avoid Data Lock-In

A connected platform should make information more useful, not make it impossible to leave.

Brilliance One can centralize more business data while still providing supported ways for authorized organizations to export and integrate information according to their operational requirements.

Data portability remains subject to permissions, security, applicable retention requirements, and the structure available for the underlying records.

Bulk Tools + API

Use files for bulk operations. Use APIs when systems need to stay connected.

Imports and exports are useful for migration, onboarding, bulk updates, reporting, and one-time data movement. Ongoing system-to-system workflows may be better served through supported APIs or integrations.

Import / Export

Bulk & Administrative Data Movement

Use supported file and bulk workflows when administrators need to move, review, migrate, or maintain significant sets of data at a defined point in time.

API / Integration

Ongoing System Connectivity

Use supported APIs and integrations when another system needs recurring or near-real-time interaction with Brilliance One rather than repeated manual file transfers.

Connected Data Operations

Tools moves information. The modules give it business meaning.

Data-management workflows can participate across CRM, financial, workforce, product, project, document, asset, industry, and other operational records within Brilliance One.

Accounts

Customers & Relationships

Import, export, validate, and maintain supported customer, contact, organization, lead, address, and relationship information.

Accounting

Financial Data

Use appropriately controlled workflows around supported invoices, vendors, transactions, classifications, and other financial information.

Human Resources

Employee Records

Manage supported workforce data through permission-aware administrative and migration workflows.

Products

Catalog & Inventory

Move supported product, pricing, catalog, inventory, identifier, and classification information where enabled.

Projects

Delivery Records

Use migration and data-maintenance workflows around supported projects, tasks, statuses, assignments, and customer delivery information.

Technology

Asset Records

Import or export supported equipment, assets, assignments, warranties, maintenance, vendors, and lifecycle information.

Documents

Files & Supporting Records

Include supported documents and related file information within approved migration and administrative workflows.

Security

Administrative Access

Apply authentication, permissions, security groups, module access, administrative controls, and available logging to sensitive data operations.

API

Connected Systems

Use supported APIs where recurring application-to-application data exchange is more appropriate than repeated bulk file movement.

Data Platform Strategy

Modern platforms import data. Brilliance extends data operations across the business.

Modern CRM platforms already provide mature CSV imports, field mapping, record updates, exports, custom-object migration, error reporting, and bulk data tools. Brilliance One applies common data-operation patterns across the customer, ERP, workforce, asset, document, commerce, industry, and operational records inside the Business Operating System.

Move

Import & Export

Bring supported information into Brilliance One or extract authorized business records for approved external use.

Control

Validate & Govern

Apply supported mapping, validation, review, permissions, and administrative controls around significant data movement.

Operate

Use the Data Throughout the Business

Continue imported information into CRM, Accounting, Projects, HR, Products, Technology, Documents, industry workflows, and other operational modules.

Data Controls

Structured movement. Controlled access. Reviewable history.

Data operations become safer and more understandable when the platform separates movement, mapping, validation, authorization, review, and history instead of treating every bulk change as a simple upload.

Imports

Guided Data Intake

Use supported templates, mapping, validation, and review to reduce avoidable migration and onboarding errors.

Exports

Controlled Data Output

Select supported records, fields, filters, and formats for authorized reporting, migration, analysis, archival, or external processing.

Validation

Detectable Data Problems

Review supported required values, formats, mappings, identifiers, relationships, and classifications before committing significant data operations.

Permissions

Administrative Control

Restrict higher-impact data capabilities to users with the appropriate organizational responsibility.

History

Operational Traceability

Maintain available activity information around supported imports, exports, uploads, mappings, and major administrative data operations.

Maintenance

Ongoing Data Quality

Continue validating, reviewing, correcting, and maintaining important records after the initial migration is complete.

Data Governance

Powerful data tools require responsible administration.

Imports, exports, bulk updates, corrections, and cleanup can affect large amounts of customer, employee, financial, operational, or regulated information.

  • Administrative permissions
  • Data ownership
  • Import authorization
  • Export authorization
  • Data-quality review
  • Retention requirements
  • Sensitive-data handling
  • Change procedures
  • Backup and recovery planning
  • Regulatory or contractual requirements

Administrative Responsibility

Bulk operations should be intentional.

Brilliance One provides data-management capabilities, but organizations remain responsible for determining who may use them, what information may be moved, how exported data should be protected, and whether imported or changed information is appropriate for its intended business purpose.

Data tools support governance. They do not replace it.

Brilliance One Core

One shared foundation. Used throughout the platform.

Core provides the relationship, communication, automation, identity, security, configuration, and administrative capabilities that support the broader Brilliance One Business Operating System.

CRM & Relationships

Accounts

Manage customers, prospects, leads, organizations, contacts, vendors, suppliers, partners, and relationship history through one connected business record.

Explore Accounts

Locations

Addresses

Maintain billing, shipping, service, customer, employee, vendor, job-site, and operational locations as reusable records connected to the business activity that depends on them.

Explore Addresses

Email, SMS & Messaging

Communications

Connect email, SMS, MMS, campaigns, templates, lists, replies, delivery activity, and communication history with the customers and business records behind every conversation.

Explore Communications

Workflow Automation

Automations

Automate supported email, SMS, tagging, notifications, delays, follow-up, and repeatable processes so people can focus on decisions while software handles routine work.

Explore Automations

Identity & Access

Users

Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.

Explore Users

Platform Protection

Security

Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.

Explore Security

Platform Configuration

Settings

Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.

Explore Settings

Data Operations

Tools

Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.

Explore Tools

Brilliance One Tools

Move the data. Keep the operation understandable.

Import, export, map, validate, review, migrate, clean, secure, and manage business information with governed administrative tools connected to the customer, financial, workforce, product, project, asset, document, and operational records throughout Brilliance One.

Build Your Estimate Discuss Brilliance One

Brilliance One • Tools • Import • Export • Validation • Migration • Data Operations