Migrate from Gauss Box Projects to monday Work Management

Gauss Box Projects map directly to monday.com Boards. We preserve the project name, description, start date, end date, and budget fields. Each Gauss Box project becomes a monday.com board with its own default group, and we configure the board structure (column set, view defaults, group naming) based on the Gauss Box project's phase configuration. Teams using multiple Gauss Box projects that share a program or portfolio may choose to consolidate into a single monday.com workspace during migration, which we scope during discovery.

Gauss Box Phases map to monday.com Groups within a Board. Phase sequencing and phase-level start/end dates migrate as Group properties or as Status column values. We preserve phase ordering within the board because monday.com Groups maintain a defined sequence. If the customer uses phase-level budgets or phase owners, these migrate to Group column values or as separate column configurations on the board.

Gauss Box Tasks map to monday.com Items. Task name, description, assignee, deadline, priority, and status migrate as native monday.com columns. The Gauss Box task status values map to monday.com Status column options, and we define the mapping during discovery by inventorying all Gauss Box task status values in use across the customer's account. Task-level dates migrate as Date columns or Timeline columns depending on whether only a deadline or a full date range is stored.

Gauss Box Subtasks map to monday.com Subitems. Subtask names, assignees, and statuses migrate into the subitem record. Subtasks inherit project and phase context from their parent task, and we resolve the parent-child relationship by creating the subitem under the migrated parent item. Note that monday.com Subitems are only available on Pro and above plans; we verify the destination plan tier during scoping.

Gauss Box Gantt chart structures are backed by task start/end dates and phase-level date ranges. We map these to monday.com Timeline columns (containing start and end dates per item) and enable the Gantt view at the board level. Dependencies between tasks map to monday.com column Dependencies, which the Gantt view renders as arrows. We flag any Gauss Box dependency types (Finish-to-Start, Start-to-Start) that require explicit configuration in monday.com's dependency model.

Gauss Box time entries (logged hours per task per user, with estimates and actuals) map to monday.com's Time Tracking column on each Item. We populate the Time Tracking column with logged hours from Gauss Box, preserving the original log date and the user who logged the time. Gauss Box budget tracking fields (hourly rates, budget estimates) migrate as Number columns or formula columns in monday.com for budget comparison. Note that monday.com Time Tracking requires the Pro plan or above.

Gauss Box Comments on tasks and projects migrate as monday.com Updates attached to the corresponding Item or Board. Comment body, timestamp, and author reference migrate. Threading in Gauss Box (if comments reply to other comments) maps to monday.com update replies where supported. monday.com Updates support mentions, which we preserve by mapping Gauss Box @-mentions of users to monday.com @-mentions of the migrated user accounts.

Gauss Box file attachments migrate as File column values in monday.com or as URL text columns referencing the attachment location. Actual file binary transfer is scoped during discovery based on attachment volume and storage tier on the source Gauss Box account. Files stored in Gauss Box's file management system are inventoried during scoping, and we flag whether to migrate file binaries (requiring download and re-upload to monday.com's file storage) or to migrate only metadata and links (leaving files in Gauss Box or an alternative document store). Storage tier limits on Gauss Box START (1GB) are factored into this decision.

Gauss Box custom fields via the attribute set system are entirely customer-defined with no fixed schema. We inventory every attribute set and custom field during discovery, cataloging field name, data type (text, number, date, dropdown, checkbox), and the objects they apply to. We map text fields to monday.com Text columns, number fields to Number columns, date fields to Date columns, dropdown selections to Status columns or Dropdown columns, and checkbox fields to Checkbox columns. The destination monday.com column type must be created before data import, and we validate data type compatibility to avoid import rejections.

Gauss Box Users (employees with unlimited employees on the platform) map to monday.com User accounts by email address. User name, email, department, and live status migrate. We resolve users by email match against the monday.com destination workspace and flag any Gauss Box users who do not have a corresponding monday.com account to be provisioned before the record migration phase.

Gauss Box User Roles and Department management with access level definitions map to monday.com's workspace member roles (Admin, Member, Viewer) and Guest accounts. We map Gauss Box role names to the closest monday.com permission level and flag external collaborator accounts (limited view or edit access in Gauss Box) for migration as monday.com Guest accounts, which have item-level and board-level access controls that may require post-migration configuration.

Gauss Box dashboard widgets (5 widget types for project health, team activity, and resource usage) do not migrate as configured dashboards in monday.com. monday.com Dashboards aggregate data from multiple boards but have a different widget model. We deliver a written inventory of every Gauss Box dashboard widget with its data source, filters, and visualization type, and the customer's admin rebuilds the equivalent dashboard in monday.com's dashboard builder post-migration.