Migrate from StrategicERP to monday CRM

StrategicERP contacts migrate as items on a monday CRM Contact board. Email, phone, and address fields map to corresponding monday text columns. Primary company link transfers via monday's connection column linking contacts to the Company board. Each contact retains its original creation timestamp and owner, mapped to monday's person column. Additional custom fields become text columns as needed.

StrategicERP companies map to monday CRM company items on a dedicated Company board. Company name, address, and industry fields become text and status columns. Parent-company hierarchies translate to monday's connection column for organizational structure. Each company item records the original created date and owner. Multi-select industry tags map to status column options in monday.

Each StrategicERP project becomes a monday CRM board. Project metadata (name, start date, budget) becomes board-level columns. Project stages translate to monday status columns matching the same stage labels from StrategicERP's workflow states. All project-level custom fields are created as additional columns. Owner assignments map to the monday person column for each board.

StrategicERP cost codes attach to projects as sub-items within the corresponding monday project board. Cost code numbers become text columns; amounts map to numeric columns. Multiple cost codes per project create multiple sub-items within one board. Each sub-item preserves the original cost code description and owner. Date fields for budget and actual amounts map to monday date columns, enabling timeline views.

Submittals from StrategicERP migrate as sub-items on the project board. Status (pending, approved, rejected) becomes a monday status column with matching values. Submission dates and approval dates map to date columns. Each submittal preserves the original description and linked attachments. Owner assignment maps to monday person column for accountability.

RFIs become sub-items on the monday project board. RFI number as text, question and response as long-text columns, status as monday status. Linked cost impact data migrates as numeric columns. Each RFI sub-item retains the original creation timestamp and owner. Attachments associated with RFIs upload to monday files column, respecting plan storage limits.

Change orders migrate as standalone items on the project board rather than sub-items. Change order number, description, approved amount, and status map to monday columns. Approval workflow states become monday status column values. Each change order item preserves the original creation date and owner. Linked cost impact data appears in numeric columns, enabling budget variance analysis.

Budget amounts and actual costs from StrategicERP's financial module transfer to monday numeric columns on the project board. Currency formatting preserved. Separate columns track budget vs. actual values for variance reporting. All numeric columns inherit the original decimal precision. Owner of the financial record maps to monday person column, ensuring accountability for budget updates.

StrategicERP project owners resolve by email match to monday CRM users. Matched users populate the monday person column on the project board. Unmatched owners flagged with the original owner name preserved in a text column for admin assignment. The resolution process runs during the audit phase and logs each match decision. If multiple monday users share the same email, the most active user is selected.

StrategicERP custom fields on contacts, companies, and projects require monday CRM column creation. Number, text, date, and status field types map directly. Dropdown-style custom fields become monday status columns with matching options. Each new column inherits the original field label and any validation rules. Complex custom fields storing structured data are preserved as text for reference after migration.

File attachments linked to StrategicERP projects, submittals, or RFIs re-upload to monday CRM files columns. File size limits per monday plan apply — files over 500MB require pre-upload to monday-integrated storage. During migration, FlitStack checks each file against the target plan's storage quota. Files exceeding the limit are uploaded to Google Drive or SharePoint, with a link stored in the monday files column.

StrategicERP automations tied to construction approval chains, stage-based notifications, and cost-code triggers do not migrate. FlitStack exports automation definitions as a configuration reference. Teams rebuild automations in monday's Automation Center using the exported specifications. The exported file includes trigger events, conditions, and action steps in JSON format. This allows monday admins to replicate logic step-by-step, including email alerts, status updates, and integration with third-party tools.