TechAppForce

Data and IT

Legacy data migration

Move records out of old tools and spreadsheets, checked before anything is saved.

Book a demoSee how it runs
  1. Uploaded
  2. Validated
  3. Approved
  4. ImportedDone
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Replacing an old system means moving years of data out of exports and spreadsheets. Imports fail halfway, lookups do not match, and the team finds bad rows only after they are already in the new system.
Who feels it: IT teams and implementation partners retiring an old system

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. The export arrivesAn implementation partner is moving a housing association off a system built many years ago. The client sends Excel exports of tenants, properties and repairs.
  2. Dry run firstThe partner runs the property file as a validation only. Forty rows reference a region spelled two different ways.
  3. Fix and approveData owner approvesThe client fixes the source file. The dry run comes back clean, and the data owner approves the batch.
  4. ImportProperties are imported with their rooms as child records in one pass. Repairs follow, linked to the right properties by lookup.
  5. Rehearsed, then realThe whole migration was rehearsed in QA. On cut-over weekend, the same files run in production.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 4

  • Target entities for the new app, such as customer, site and contract0 fields + history, files, comments
  • Import batch5 fields + history, files, comments
  • Lookup lists4 fields + history, files, comments
  • Parent and child records, such as order and order lines0 fields + history, files, comments

Stages 4

  1. Uploaded
  2. Validated
  3. Approved
  4. Imported

Automatic 4

  • WorkflowA validate-only dry run reports errors row by row without saving anything
  • WorkflowLookups are resolved by name, so a spreadsheet can say “North region” instead of an id
  • WorkflowChild records are imported with their parents in the same file
  • WorkflowBulk updates fix a field across many records after import

Screens and reports 4

  • Import screen with the row-level error list
  • Data grid of imported records for spot checks
  • Import summary by batch, in Excel
  • Reconciliation counts per entity as a CSV
Who approves, in detail

Before a batch is processed, the data owner for that entity approves the validation results (record field strategy).

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Entity: property

Fields
Added: + Legacy reference
Added: + Region (lookup)
Reference data
Added: + Regions North · South · East
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.