Exporting data from LiquidPlanner is a critical phase of the migration. The platform allows exports in various formats, including CSV and Excel. However, not all data will export cleanly. Complex dependencies, custom fields, and historical time entries may require manual handling. Start by exporting the core data: projects, tasks, assignments, and due dates. Then export resource information and time tracking records separately. Keep the exports organized in a folder structure that mirrors your project hierarchy. This makes it easier to map fields when importing into the new system.
The next step is mapping LiquidPlanner fields to the new platform’s fields. For example, a “task” in LiquidPlanner might be called an “issue” or “work item” in another tool. A “resource assignment” might map to a “user allocation.” A detailed comparison on Medium (
https://medium.com/@johan-winther/liquidplanner-alternatives-621c9827e661) provides guidance on how different platforms structure their data, which helps with mapping. Create a mapping document that lists each source field and its destination. Then import a small sample of data and verify that it appears correctly. Check for missing dependencies, incorrect dates, and lost assignments. Fix mapping errors before importing the full dataset.
Once the sample import is accurate, proceed with the full export. Import in batches to avoid overwhelming the system. After each batch, run a validation check. Compare task counts, milestone dates, and resource assignments against the original LiquidPlanner data. Document any discrepancies and resolve them. This methodical approach ensures that your new platform starts with clean, accurate data. Rushing the export and import process often leads to corrupted records and frustrated users, so take the time to get it right.
