Migrate from QuickStart Admin to monday Work Management

QuickStart Admin projects map to monday.com boards as the top-level container. We use the board name from QuickStart Admin's project name and set the board type to Shareable or Private depending on the source project's visibility setting. Board structure (Groups, columns) is built per the destination schema during migration day. If QuickStart Admin exposes multiple projects, each maps to a separate board; we create a monday.com Workspace or Folder to group them if the project count exceeds five.

QuickStart Admin task records map to monday.com items on the corresponding board. Standard fields (task name, description, due date, priority, status) map to monday.com column types: Status column for status, Date column for due dates, Person column for assignees, and Text or Long Text columns for descriptions. The item is inserted using the monday.com create_item mutation with board_id resolved from the project mapping.

QuickStart Admin subtask records map to monday.com subitems when the source platform exposes a parent-child relationship. Subitems in monday.com are independent items with their own columns, assignees, and updates, attached to the parent item. We resolve the parent item_id from the QuickStart Admin task mapping and create subitems using the create_subitem mutation. Subitem ordering is preserved by setting a subitem position index.

QuickStart Admin assignee references map to monday.com team members by email match. We extract all distinct assignee email addresses from QuickStart Admin task records during the pre-flight audit and validate them against the monday.com workspace before migration. Users present in QuickStart Admin but not in monday.com are held in a reconciliation queue; the customer's admin provisions the missing accounts before the assignee phase runs.

QuickStart Admin custom fields (field-level metadata not confirmed in public documentation) map to monday.com column types based on the inferred data type: text fields map to Text or Long Text columns, numeric fields to Number columns, date fields to Date columns, picklist fields to Status columns with defined labels, and boolean fields to Checkbox columns. We generate the column schema during the pre-flight audit by probing the customer's live QuickStart Admin instance and building a custom field map before migration day.

QuickStart Admin comment records map to monday.com Updates attached to the parent item. We extract comment body, author email, and timestamp during the pre-flight audit. Updates are created using the monday.com add_update mutation with the item_id and user_id resolved from the task and user mappings. Rich text formatting in comments may simplify to plain text during transfer depending on the source export fidelity.

QuickStart Admin user accounts (admin, member, or guest roles if confirmed) map to monday.com users by email. We extract all distinct user emails during the pre-flight audit and map roles to monday.com permission levels (owner, admin, member, viewer) based on QuickStart Admin role metadata. Inactive or archived QuickStart Admin users are mapped to inactive monday.com users to preserve historical assignment data without granting active login.

QuickStart Admin file attachments cannot be confirmed for migration without a verified API or export endpoint. If the pre-flight audit confirms a file-based export mechanism, we migrate attachments as URL columns pointing to a temporary hosted location, or as File column uploads if the destination monday.com plan supports file storage. monday.com Standard and Pro plans include file storage; Free and Basic plans have limited attachment capacity. We flag this during scoping and recommend a file migration strategy before migration day.

If QuickStart Admin exposes team or group structures beyond individual user assignments, these map to monday.com Teams created in the destination workspace. Teams in monday.com allow group-based board sharing and permission scoping. We probe for team-level groupings during the pre-flight audit and create monday.com Teams via the teams mutation before board migration begins.

QuickStart Admin task status values (e.g., To Do, In Progress, Done) map to monday.com Status column labels on each board. We extract all distinct status values during the pre-flight audit, create matching Status column labels in monday.com during board setup, and map each QuickStart Admin task status string to the corresponding label during item migration. Color mapping follows monday.com default conventions unless the customer specifies a color scheme during scoping.

QuickStart Admin priority values (if confirmed in the source data model) map to monday.com Label columns with color-coded labels or a numeric priority column. The mapping depends on whether QuickStart Admin exposes discrete priority levels or a numeric score. We confirm the priority field format during the pre-flight audit and configure the destination column type accordingly.

QuickStart Admin due dates map to monday.com Date columns on each board. If QuickStart Admin exposes a start date in addition to a due date, we create a Timeline column in monday.com (Pro and Enterprise) or two separate Date columns for start and end. Timezone handling is reconciled during the pre-flight audit by comparing QuickStart Admin timestamps against the destination workspace timezone setting.