Migrate from 24SevenOffice to monday Work Management

24SevenOffice Projects map 1:1 to monday.com Boards. We create a board per project, setting the project name as the board title, project start/end dates as board labels or a Date Range column, and project budget as a Number column. Milestones are modeled as Group rows or as a dedicated Milestone column type (Pro tier) depending on the destination plan. The project owner is added as a board subscriber and optionally as a board admin.

24SevenOffice Tasks migrate to monday.com Items within their parent board. We preserve parent-child hierarchy by placing child tasks as subitems under the parent Item (monday.com subitem feature, Pro tier and above) or as separate Items grouped under a parent group. Assignees, due dates, estimated hours, and task status transfer directly to the relevant monday.com column types. Custom task fields become custom columns, with type mapping performed during discovery.

24SevenOffice Subtasks map to monday.com Subitems when the destination account is on the Pro plan or above. Subitems inherit the parent item's board context and can have their own assignees, due dates, and status. Standard-plan accounts without subitem access receive subtasks as separate Items within a dedicated Subtasks group on the board.

24SevenOffice Time Entries link to Projects and Users and carry billable/non-billable flags, timestamps, and duration. We model these as Number columns (for hours logged) and Timer columns (for running time tracking) on each task's Item. Billable flag becomes a Status or Checkbox column. Time-entry-to-project rollup is represented as a formula column summing child item time columns to the board level. Note: monday.com does not have a native accounting module; invoice generation from time entries requires a third-party integration post-migration.

24SevenOffice CRM Contacts migrate to Items in a dedicated Contacts Board. Each contact's name, email, phone, address, lifecycle stage, and owner map to monday.com Text, Email, Phone, Location, Status, and Person columns respectively. Tags from 24SevenOffice become Labels columns or Integration Automations that tag items. Custom contact properties map to custom columns based on their field type during discovery.

24SevenOffice Company records transfer as Items in a Companies/Accounts Board or as Groups within the Contacts Board, depending on whether the customer uses monday.com CRM. Company name, industry, size, and address map to equivalent column types. Associated contacts are linked by creating cross-board reference items or using the monday.com integration automations to connect related records.

24SevenOffice Deals require significant schema redesign because monday.com has no native Deal or Opportunity object. We model each 24SevenOffice deal pipeline as a monday.com Board with Groups representing deal stages (e.g., Prospect, Qualified, Proposal, Negotiation, Closed Won, Closed Lost). Deal value, close date, and contact association migrate to Number, Date, and Person columns on each deal Item. Stage transition history is preserved as Status column updates logged via the monday.com Activity Log API.

Each 24SevenOffice pipeline stage maps to a monday.com Group within the deal board. We preserve the stage order, probability mapping, and stage duration by configuring Groups in sequence and adding a Number column for probability percentage. The customer defines the stage-value mapping during scoping.

24SevenOffice Invoices carry line items, tax codes, payment status, and country-specific accounting metadata. monday.com has no native accounting or invoicing module. We extract invoice records as a separate export (CSV or JSON) for the customer's accounting team to reconcile in their destination accounting software. Within monday.com, we add a Number column referencing the invoice identifier and a Status column for payment state (Paid, Unpaid, Overdue). 24SevenOffice's country-edition tax codes (Norwegian, Swedish, UK) are preserved in a text column for reconciliation purposes.

Custom fields on any 24SevenOffice object (Project, Task, Contact, Company, Deal) are explicitly mapped to monday.com column types during discovery. Text fields become Text columns; dropdowns become Status columns with configured labels; numbers become Number columns; dates become Date columns; Boolean flags become Checkbox columns. We inspect the source schema during discovery and flag any field types that do not have a direct monday.com equivalent (e.g., multi-select arrays stored as delimited text require a workaround).

File attachments on 24SevenOffice Projects, Tasks, and Invoices are referenced by URL in the API. We download attachments to temporary storage, then re-upload to the destination monday.com Board Item using the monday.com File API, preserving the association to the correct board and item. The File column type (Pro tier) stores the file directly on the item; Standard accounts receive file URLs stored in a Text column with a file link label.

24SevenOffice flat key-value tags applied to Contacts, Companies, and Deals migrate to monday.com Labels columns (Pro tier) or Status columns with tag names as labels (Standard tier). We extract all tag values during discovery, configure the column in the destination board before import, and apply tags post-import using the monday.com API. Tags used for deal segmentation are preserved on the deal board as Labels columns for filtering.