Migration

Move to Batoi Flex without losing useful history

Batoi provides a structured migration service for customers who need to retain website content, form submissions, customer interactions, engagement evidence, files, billing history, vendor records, and compliance artefacts while moving to Flex.

Migration is quoted separately from the subscription. A detailed quote is provided after discovery and source-system review.

Historical data migration flow Source systems move through discovery, mapping, trial migration, validation, and cutover into Batoi Flex. Legacy Site CMS, forms, CRM Historical Data files, logs, reports Map clean, match, test Flex validated Discovery -> Trial -> Validation -> Cutover

Historical data can be retained

Retention is planned from the source platform, export format, data quality, compliance requirements, and target Flex modules.

A standard process is available

Discovery, inventory, mapping, extraction, transformation, trial migration, validation, final cutover, and post-migration support.

Quoted as a special service

High-level ranges help early planning. A formal quote follows after infrastructure details and scope are shared.

Three retention levels

The right level depends on how much historical data must remain searchable, operational, analytical, or audit-ready after migration.

Level 1

Historical Archive

Preserve old records as searchable files, tables, or evidence exports for reference and compliance needs.

  • Legacy submissions and files retained
  • Searchable reference archive
  • Lower mapping complexity
Level 2

Structured Import

Map forms, contacts, inquiries, files, invoices, vendors, and customer interactions into the relevant Flex modules.

  • Operational records become usable
  • Relationships are preserved where possible
  • Best fit for Business and Scale customers
Level 3

Enhanced Migration

Add cleansing, deduplication, relationship mapping, analytics reconstruction, and compliance evidence preparation.

  • Data quality improvement
  • Audit and retention alignment
  • Suitable for compliance-heavy scopes

Standard migration process

The process gives prospects confidence that migration is not experimental, while keeping the final scope dependent on source-system access.

1 Discovery
2 Data Inventory
3 Mapping
4 Extraction
5 Transformation
6 Trial Migration
7 Customer Validation
8 Final Cutover
9 Post-Migration Support
Estimate Planner

Build a planning estimate for migration

Select the data areas and migration conditions that look closest to your current setup. The result is an early planning range only, not a formal quote.

Data areas to migrate

Select one or more

Retention level

Data volume

Source access

Compliance sensitivity

What we need before a quote

A reliable quote requires enough source detail to judge access, mapping complexity, data cleanup effort, and validation responsibility.

Share Migration Details
Current platform and hosting details
Export, database, or API access method
Approximate record counts by module
Storage size and file types
Analytics source and export availability
Compliance and retention requirements
Target go-live date
Legacy system availability window
Data residency and consent constraints

What can usually be retained

Pages, media, redirects, form submissions, contacts, notes, interactions, documents, invoices, vendor records, and compliance evidence can usually be preserved when source exports or access are available.

What depends on the source system

Event-level engagement analytics can only be reconstructed if the source provides raw logs or exportable event data. Otherwise, reports and summaries can be archived for reference.

Plan the move before changing the website

For Scale, Business, and compliance-focused customers, migration should be scoped before commitment so historical records, validation effort, and cutover timing are clear.

Start simple. Built for the way small businesses actually operate.