Migrate from .STUDIO to monday Work Management

STUDIO Projects map to monday.com Boards. Each .STUDIO project becomes a standalone Board with the project name as the Board name, project status preserved as a Status column, and project dates mapped to a Timeline column. If the .STUDIO workspace uses multiple project types (retainer, project-based, internal), we create Board Folders in monday.com to group them by type. The project-client linkage is preserved by linking the board to a Companies integration entry or a client-tracking board.

STUDIO Tasks map to monday.com Items within the target Board. Each task's name, description, assignee, due date, estimated hours, and status map to corresponding Item fields. Subtasks in .STUDIO map to Subitems in monday.com if the destination account has Subitems enabled on the board. Task hierarchy is preserved by ordering Subitems under their parent Item. Custom field values on tasks map to typed monday.com columns (date, number, dropdown, checkbox).

STUDIO Client records map to monday.com Companies (via the native Companies integration) or to a dedicated client-tracking board if the destination account does not have the Companies integration active. Client name, contact info, billing details, and hourly rate transfer to the Company record or equivalent board columns. We preserve the project-client linkage by adding the Company as a Connected Entity to the relevant Board or by linking via a Client Name column pointing to the Company record.

STUDIO Time Entries map to the monday.com Time Tracking column on the target Board, with each time entry creating a time block linked to the corresponding Item. Duration, date, user, and notes transfer to the time block. Billable flag from .STUDIO maps to the billable toggle if available on the monday.com plan; otherwise it is stored as a checkbox column. We flag the 6-minute rounding default in .STUDIO during scoping and allow customers to choose whether to preserve source rounding or align to the destination default.

STUDIO custom field definitions are read at migration time from the active workspace schema. Each .STUDIO custom field type (text, number, date, dropdown, checkbox, formula) maps to the nearest monday.com column type. Formula fields referencing other custom fields are not natively supported in monday.com columns; we fall back to plain-text and note the limitation in the migration manifest. Multi-select dropdowns in .STUDIO map to monday.com Tags or multi-select columns depending on the expected use pattern.

STUDIO User records (name, email, role, hourly rate) map to monday.com Workspace Members. We resolve by email match and map the .STUDIO hourly rate to a custom number column on the user's profile or to a rate column in time-tracking boards. Users without a matching monday.com account go to a reconciliation queue for the customer's admin to provision before migration resumes.

STUDIO Tags are flat string labels applied to tasks and projects. They map to monday.com Tags on Items. If a .STUDIO workspace uses a structured tagging taxonomy (e.g., service-type, department, priority), we discuss whether to preserve tags as monday.com Tags or convert them to a Status or Labels column for filtering and board views.

STUDIO File attachments (filename, URL, size, type) map to the Files column in monday.com. We export attachment metadata and re-attach files at the destination. Note that .STUDIO stores file attachments externally; if the source URL becomes inaccessible after migration, the attachment metadata is preserved in the migration manifest but the file itself may not re-attach. We flag inaccessible URLs during the export phase and report them in the migration manifest.

STUDIO Comments attach to tasks and carry author, timestamp, and text body. They map to monday.com Updates on Items. Author and timestamp are preserved. If comments contain @mentions, the mention syntax does not migrate automatically; we note this in the manifest and recommend reviewing mentioned-user notifications after migration.

STUDIO Project and task templates are reusable blueprints. We export the template structure (board layout, column types, group names, task naming patterns) as a written template spec. We do not replicate .STUDIO templates inside monday.com directly because the template models differ; instead, we deliver a board-template creation guide mapped to the .STUDIO template structure so the customer's admin can build equivalent templates in monday.com.

STUDIO Invoices live in a separate billing submodule that is not part of the core PM data model. We do not migrate invoice records. If the customer uses .STUDIO's invoicing feature and will move billing to another platform (QuickBooks, Xero, FreshBooks), we provide a CSV export of invoice records for import into the billing destination separately.

STUDIO project budget fields are optional and frequently left blank. We export budget values where present and map them to a custom Number column (Currency type) on the destination Board. We flag records with missing budget data in the migration manifest and surface them during the scoping call so the customer can set defaults or accept null values. monday.com does not have a native budget field; budget tracking requires a custom column or a third-party budgeting integration.