Hi everyone,
Data migration is a critical step when transitioning from spreadsheets or legacy systems into ActivityInfo. Done well, it improves data quality, strengthens reporting, and sets a solid foundation for future workflows. Done poorly, it can introduce inconsistencies and long term data integrity issues that are difficult to correct later.
A successful migration starts with carefully reviewing and cleaning existing data, clarifying relationships between datasets, and thoughtfully designing your target schema. Instead of replicating spreadsheet structures, it is important to define required fields, key and unique constraints, reference data, and validation rules intentionally. Testing imports in small batches and validating record counts before a full rollout significantly reduces risk.
For a detailed step by step approach, you can read the full documentation here:
https://www.activityinfo.org/support/docs/working-with-data/migrating-data-to-activityinfo-best-practices.html