Migrate from TimeLog to monday Work Management

TimeLog Projects map to monday.com Boards, with each Project becoming a dedicated Board containing Activities as Items. For organizations with fewer than 10 active projects, a single Board with Activity Groups is a simpler alternative. Project status (active, on hold, completed) maps to a Status column on the Board. Project-level custom fields from TimeLog become Board-level columns or Item-level custom fields, and are flagged for post-migration validation against the monday.com column type schema.

TimeLog Activities map to monday.com Items within the parent Project Board. Each Activity carries its rate type (hourly, fixed, milestone), billing method (time-and-material, fixed-price), and budget type. These PSA-specific properties do not have native monday.com equivalents; we map rate type to a Text or Formula column and flag that billing logic requires a third-party PSA integration or a custom monday.com workbook to replicate.

TimeLog Time Entries map to monday.com Item-level Time Tracking columns. Each entry carries date, hours, billable/non-billable flag, description, and the employee attribution. We resolve the employee attribution to a Person column on the Item. monday.com's Time Tracking column is scoped to the Item—employees log time against specific Items rather than against Activities system-wide. Teams that rely on a global timesheet view must configure a separate Work Log board or use a third-party time tracking integration.

TimeLog Employee profiles (name, email, role, department, billing rate) map to monday.com Person column values and a parallel Contacts board that stores the full employee profile. We create the Contacts board first as a lookup reference, then resolve Person column assignments during Item migration. Salary administration records (tier-gated on TimeLog Starter) migrate only where present in the source account and are flagged for the customer's HR system as a separate destination.

TimeLog Customers (billing entities associated with Projects) map to a monday.com Contacts board with name, email, billing address, and currency fields. Customer-Project associations are preserved by adding a Person column (for customer contacts assigned to Projects) and a Text or Link column (for the Account-level association to the Project Board). Currency settings map to a Text or Number column since monday.com does not have a native multi-currency field.

TimeLog Invoices do not have a native monday.com equivalent. monday.com has no billing or invoicing engine. We flag Invoices as a record type requiring a separate PSA integration (Cerri, Accelo, Function) or manual rebuild. Invoice headers and line items can be migrated to a separate Invoice board for historical reference, but the invoice-to-activity linkage and payment status tracking require a non-monday.com tool to function.

TimeLog Expenses migrate to a separate Expenses board with amount, date, category, billable flag, and the parent Project lookup. Expense-to-invoice associations are preserved as a Text or Relation column linking to the Invoice board Item. Billable expenses are flagged with a Status or Labels column. Non-billable expenses migrate as read-only historical records.

TimeLog Resource Allocations (Employees allocated to Projects by hours or percentage) map to monday.com Person column assignments with a Timeline column defining the allocation window. The Workload view in monday.com Standard+ provides a capacity visualization equivalent to TimeLog's resource planning view. Allocation percentage is stored as a Number column; where TimeLog uses percentage-based allocation, we compute and store the equivalent hours based on the Project's total estimated hours.

TimeLog maintains employee rates, Activity rates, and customer-specific pricing. These rate structures map to monday.com Number and Text columns on the relevant Items (Employee profile on Contacts board, Activity Items). Rate type (hourly, fixed, milestone) maps to a Labels or Status column. The rate mapping is flagged for customer review because monday.com does not enforce rate-based billing—rate values are informational unless connected to a billing integration.

TimeLog custom fields on Projects and Activities map to monday.com column types based on the field data type: text fields become Text columns, numbers become Number columns, dates become Date columns, and multi-select values become Labels or Dropdown columns. Extended field definitions are queried during discovery. Custom field values are migrated as available and flagged for post-migration validation to catch any schema mismatches between the TimeLog definition and the monday.com column configuration.

Salary administration is a TimeLog higher-tier feature that may not exist in every account. Where salary records are present (Professional and Enterprise tiers), we confirm during discovery whether they are in scope. Salary data typically routes to an external HR system rather than monday.com, which is a work management platform with no payroll or compensation module. We migrate salary records as a historical reference to a separate HR board or flag them for the customer's HRMS as a separate migration.

TimeLog's reporting views are generated dynamically from transactional data and are not exportable as static reports. We do not migrate report definitions or saved report configurations. The underlying transactional data—Projects, Activities, Time Entries, Expenses—is migrated to monday.com, where teams rebuild reports using monday.com's Dashboard and chart widgets. We deliver a written inventory of TimeLog report names and their source objects to guide the rebuild.