Identify the source
Understand the systems, files, exports, identifiers, and history the customer needs to preserve.
Bring Your Existing Data
Changing systems should not mean abandoning operational history.
Turnover’s migration direction is to import, map, normalize, and preserve useful historical context where practical, including external IDs and source references, while using assisted migration for complex customers.
Import and map where practicalPreserve source referencesAssisted path for complex migrations
Migration without throwing history away
Existing dataCSV, Excel, structured exports, databases
→Map & normalizeContext, IDs, dates, equipment
→Useful historySearchable inside the new operating model
A deliberate migration process
Move the data that deserves to keep working.
Map the structure
Align source locations, equipment, IDs, people, dates, work references, and useful history to the Turnover program structure.
Normalize carefully
Import or transform data in a way that preserves meaning and avoids pretending every legacy field maps perfectly.
Preserve references
Keep external IDs and source references where practical so historical records remain traceable.
Validate with users
Confirm that the migrated history is understandable and useful to the people who will search it.
Cut over at the right level
Use Turnover as complementary or primary based on the customer’s actual operating and system requirements.
Planning your import
Plan and validate the import path before a full migration.
Before migrating, we review representative records, confirm what your current Turnover deployment can import, and agree on any preparation or assisted mapping that is needed.
- Sample CSV or spreadsheet exports can help us evaluate fields and mapping; import support is confirmed before implementation
- Database or system exports can be reviewed for a separately scoped migration
- Complex source structures may require assisted mapping and cleanup
- Direct connectors are considered separately; we do not assume one exists for your system
- Any proposed integration is documented as available, assisted, or not yet supported before work starts
Sometimes migration is not the first move
Complement firstLOWER DISRUPTION
Run Turnover alongside the current stack and prove value before changing systems of record.
Migrate laterWHEN READY
Consolidate only when the operational and commercial case is clear.
Before your rollout
What can you plan on today?
Turnover can start as a separate, useful workflow. System connections and imports depend on your actual source data, approvals and supported implementation path.