Data migration
How to Migrate Existing Lab Data into TissueCulture Pro
Adopting new lab software is easier when existing records can come with you. TissueCulture Pro includes a Basic Data Import workspace for moving structured spreadsheet data into the app with templates, column mapping, validation, and import history.
Key takeaways
- Import structured CSV or XLSX files instead of retyping common lab records by hand.
- Use templates and column mapping for plants, media formulations, media preparations, cultures, inventory catalog items, and inventory lots.
- Validate rows before committing so problems can be corrected before data enters the system.
- Preserve source IDs where supported so old spreadsheet or legacy-system references remain easier to cross-check.
Start with clean structured files
TissueCulture Pro's Basic Data Import is designed for structured spreadsheet data, not messy free-form notes. Prepare CSV or XLSX files with one record per row and clear column headers.
This is where the educational migration work still matters: old spreadsheets often need cleanup before import. Standardize names, dates, statuses, IDs, and required fields before bringing the data into the app.
Import records in the right order
Some records depend on others. TissueCulture Pro guides users through import scopes so foundational records come first and dependent records can reference them later.
A common migration path starts with mother plants, then media formulations, then media preparations and cultures, followed by inventory catalog items and inventory lots when lot traceability is needed.
- Plants and accession records
- Media formulations
- Prepared media batches
- Current culture line records
- Inventory catalog items
- Inventory lots
Map columns, validate, then import
Upload the file, map source columns to TissueCulture Pro fields, and run validation before committing the import. The importer can identify missing required fields, invalid values, and rows that need correction.
Only rows that pass validation should be imported. If errors are found, export the error details, fix the source file, and run validation again.
Keep old IDs as cross-references
Many labs already have plant IDs, media IDs, culture IDs, or batch IDs in spreadsheets or an older system. TissueCulture Pro import fields include source ID options for several record types so those old references can remain available for cross-checking.
The app can assign its own native IDs while still preserving source identifiers where supported, which helps the team reconcile imported records during the transition.
Put this into a working system
TissueCulture Pro is built to turn these record-keeping ideas into connected plant tissue culture workflows.
See spreadsheet migration workflowsQuick answers
Can TissueCulture Pro import my existing spreadsheet data?
Yes. The Basic Data Import workflow supports structured CSV or XLSX files for common records such as plants, media formulations, media preparations, cultures, inventory items, and inventory lots.
Does the importer validate data before saving it?
Yes. The workflow includes mapping and validation before the import is committed, so users can correct problems first.
Can old IDs be preserved?
Where supported, source ID fields let labs keep old spreadsheet or legacy-system identifiers as cross-references while TissueCulture Pro uses app-native records.