Migrate from GBuilder to monday CRM

Each GBuilder project becomes a Monday CRM board. Project name maps to board title, project description maps to the board's overview text. Board groups are created to mirror GBuilder's section or phase breakdown within each project. The workspace structure (folder organization in GBuilder) maps to Monday workspaces or sub-workspaces.

GBuilder tasks map directly to Monday items. Task name becomes the item title, task description maps to the item's main text column, and assignment, due date, priority, and status map to Monday column types (person, date, dropdown, status). Sub-tasks in GBuilder map to Monday sub-items within the parent item.

GBuilder contacts stored with a project link migrate to Monday CRM Contacts (Standard plan or above) with the project association stored as a text column or linked item. If Monday CRM is not active, contacts migrate as items in a dedicated Contacts board with Name, Email, Phone, Role, and Project columns created as custom columns.

GBuilder companies map to Monday CRM Accounts with company name, domain/website, industry, employee count, and annual revenue stored as Account columns. Company-to-contact associations are preserved via the contact's linked Account field. Multiple project associations per company are stored as a linked items column.

GBuilder deal records (if present) map to Monday CRM Deals with deal name, amount, stage, expected close date, and owner. Pipeline stages in GBuilder map to Monday's Pipeline columns with stage values preserved. If GBuilder deals are stored as tasks with a custom deal stage property, those tasks migrate as items in a Deals board with the stage column mapped accordingly.

GBuilder deal pipelines become Monday CRM Pipelines. Each pipeline stage name maps to a Monday stage value within the Pipeline view. Stage ordering and probability percentages are preserved as pipeline configuration. If GBuilder has multiple pipelines, each becomes a separate Monday Pipeline.

GBuilder file attachments are downloaded and re-uploaded to the connected Google Drive or SharePoint account linked to Monday CRM. A file URL column in Monday links back to the re-hosted attachment. Original file names and upload timestamps are preserved as column metadata. Monday's 500MB per file storage limit applies after re-hosting.

GBuilder custom properties scoped to a project type create Monday custom columns scoped to that board. Engineering data types (measurement fields, specification text, material codes) map to Monday column types: numeric columns for measurements, text columns for codes, dropdown columns for specification types. Custom property validation rules do not transfer — column validation must be configured in Monday after migration.

GBuilder activity history (logged calls, emails, meeting notes) migrates as Updates on the relevant Monday item, with the original timestamp and owner preserved in the update text. If Monday CRM's Email & Activities add-on is active, activities are created as CRM Activity records linked to the Contact or Deal. Monday's activity log retention is plan-dependent (Basic: 1 week, Standard+: longer).

GBuilder users are matched to Monday.com workspace members by email address. Owner assignments on tasks and deals transfer as the person column in Monday. If a GBuilder user has no Monday account, records are assigned to a designated fallback owner and flagged for admin review before go-live.

GBuilder's parent-child project relationships map to Monday board groups within a single board or to the Relation column type linking items across boards. Multi-level sub-project hierarchies deeper than two levels may require flattening or custom board groupings — FlitStack surfaces this in the pre-migration schema plan.

GBuilder task comments and notes migrate as Monday Updates on the corresponding item. Original author and timestamp are preserved in the update attribution. Rich-text formatting in GBuilder notes is simplified to plain text in Monday Updates. If GBuilder comments include file attachments or @mentions, those references are captured as plain text links or usernames within the update body.