Migrate from TimeLog to Trello

TimeLog Projects map to Trello Boards. We preserve the project name as the board title, project status (Active/Completed/On Hold) as board star or archive, and the project start and due dates as card due dates on the first imported card. The project description maps to the board description field. Trello does not support nested sub-projects, so multi-level project hierarchies in TimeLog flatten into a single board level and are documented for manual restructuring post-migration.

TimeLog Activities map to Trello Cards. Each Activity name becomes a card title, the Activity description maps to the card description, and the Activity status (Active/Completed) maps to card archive state or a label. The billable/non-billable flag becomes a Trello label (e.g., 'Billable' or 'Non-Billable'). The Activity budget type (fixed-price or time-and-material) is preserved as a card label, though the budget amount itself has no Trello field to map to. Customers should note that budget tracking requires a separate financial system after migration.

TimeLog Time Entries do not have a native Trello equivalent. We migrate the total logged hours per Activity as a card label (e.g., 'Logged: 14.5h') and per employee as a checklist item for reference. For paid-tier migrations, we document the Power-Up to use for ongoing time tracking (Time Tracking & Reporting Power-Up or a third-party like Planyo or Toggl Button integration). Historical time entry data is preserved as card metadata and exported as a CSV alongside the board migration for any time-and-billing reconciliation needed after cutover.

TimeLog Employees map to Trello Workspace Members. We use the employee's email address as the Trello account identifier. Board membership is granted based on which projects the employee was assigned to in TimeLog. Card assignment in Trello maps to the employee's activity assignments in TimeLog. Trello does not support employee roles, departments, or billing rates, so these are preserved in a CSV export alongside the migration for reference. Salary data is not migrated because Trello has no payroll object.

TimeLog Customers map to Trello in one of two ways depending on migration scope. For small customer lists, we create a Trello label per customer (e.g., 'Client: Acme Corp') and apply it to all cards within the customer's project board. For larger customer lists, we create a separate Customers board with a card per customer, and the original project board links are documented for reference. Customer contact details (address, billing currency) have no Trello field and are included in the customer CSV export.

TimeLog Invoices have no Trello equivalent. Invoice headers, line items, amounts, and payment status are exported as a structured CSV file and delivered alongside the board migration. Customers are responsible for migrating invoices to a dedicated billing platform (e.g., FreshBooks, QuickBooks, Zoho Invoice) if they require an ongoing invoicing system. We document the invoice-to-board association so that the project context for each invoice is preserved in the CSV.

TimeLog Expense records (amount, date, category, billable flag, project association) have no Trello equivalent. We export all Expense records as a CSV file linked to the corresponding project board. Customers moving from TimeLog to Trello should plan to manage expense tracking in a separate tool (spreadsheet, dedicated expense app, or accounting software) post-migration.

TimeLog maintains employee rates, activity rates, and customer-specific pricing that underpin its billing model. Trello has no rate or pricing object. We export the full rate structure as a CSV linked to the activity mapping so that the billable rate history is available for reference if the customer implements billing in a separate system. Rate migration to a billing platform is outside Trello migration scope.

TimeLog resource allocations (employee-to-project hours or percentage assignments) map to Trello card assignments. An allocation of an employee to a project becomes that employee being added as a member to the relevant project board and assigned to the corresponding cards. Trello does not support capacity planning, utilization dashboards, or conflict detection for overlapping allocations; these capabilities require a dedicated resource management tool post-migration.

TimeLog custom fields on Projects and Activities migrate to Trello's Custom Fields Power-Up where field types are compatible (text, number, date, dropdown). Trello's Custom Fields Power-Up is available on Standard ($5 per user) and above. Custom field definitions are extracted during discovery, and values are mapped to the equivalent Trello field type. Fields with data types not supported by Trello (e.g., complex picklists, calculated fields, multi-currency) are flagged and exported as CSV alongside the migration.

TimeLog Salary Administration (compensation history, effective dates, payroll data) is tier-gated and may not exist in all TimeLog accounts. Salary data is not migrated because Trello has no payroll object. If the customer requires ongoing payroll management, they should maintain salary administration in a dedicated HR or payroll system. Salary data, if present, is exported as a separate HR CSV outside the Trello migration scope.

TimeLog Reporting views are generated dynamically from transactional data and are not exportable as report definitions or saved configurations. We do not migrate report definitions. The underlying transactional data (Projects, Activities, Time Entries) migrates to Trello, and customers can rebuild reports in Trello Power-Ups (Blue Cat Reports, Dashcards) or in a separate analytics tool. A written inventory of every TimeLog report definition is delivered as a reference document for manual rebuild.