Migrate from ServeManager to monday CRM

Each ServeManager Job becomes one Item on a 'Serve Jobs' monday CRM board. The board's default group columns (Status, Due Date, Priority) map to Job.status, Job.due_date, and a custom priority column. Job type (service type) becomes a Labels or Dropdown column.

The client (law firm or individual) referenced in Job.company_id is migrated as a linked Item on a separate Clients board using monday CRM's Connect Boards column. This bidirectional link preserves the client-to-job relationship without duplicating client data across multiple job records. The Clients board also stores client-specific details like billing terms and contact information for reference on individual job items.

Each Attempt on a Job becomes a Subitem of the corresponding Item. Subitem columns capture attempt number, date/time, GPS coordinates as a Text column, disposition code, photos as file attachments, and electronic signature status. Monday CRM Subitems inherit the parent Item's board context automatically.

If your team prefers a flat log over subitems, FlitStack creates a separate 'Attempts Log' board where each Item represents one attempt, with a Connect Boards column linking back to the parent Job Item. This requires a custom 'Job Reference' column created in Monday CRM before migration.

ServeManager Companies are merged into monday CRM's dual-record structure: Company name becomes the Organization name, while the primary contact name and email create a linked Contact record under that Organization. Physical address, phone number, and billing terms migrate as additional columns on the Organization, providing a complete client profile in the Monday CRM Contacts section.

Each ServeManager Invoice is created as a separate Item on a dedicated Invoices board. The Item captures invoice number, invoice date, total amount, payment status (Paid/Unpaid/Overdue), and due date in dedicated columns. Any Stripe payment reference stored in ServeManager's payment record migrates as a text field for reconciliation purposes.

ServeManager Payment records are migrated as Items on the Invoices board or a linked Payments board, with a Connect Boards column establishing the relationship to the originating Invoice Item. Each Payment Item stores payment date, payment amount, payment method, and the Stripe transaction ID from ServeManager for cross-referencing payment records against bank statements.

ServeManager Server Payables have no monday CRM equivalent. FlitStack creates a 'Processor Payroll' board where each Item represents a payable record, with columns for processor name (linked Contact), job reference (Connect Boards to Serve Jobs), rate, amount, and payment status. Your admin configures compensation-rate logic as Monday formulas after migration.

ServeManager file attachments — including affidavits, proof-of-service documents, and uploaded files — are migrated as Files attached directly to the corresponding Job Item in monday CRM. The original filename and original upload date are preserved as metadata. Monday CRM's file storage limits apply based on your plan tier, with the Enterprise plan offering expanded storage capacity for high-volume attachment archives.

ServeManager custom fields on Jobs map to monday CRM custom columns on the Serve Jobs board. Column type is inferred from the source field type: text fields → Text, dates → Date, options → Dropdown or Labels. Your admin reviews and assigns the correct monday column type during the pre-migration schema review.

ServeManager stores GPS latitude and longitude separately per attempt. FlitStack combines these into a single Text column ('GPS Coordinates') in standard 'latitude, longitude' format (e.g., '39.7385, -104.9855'). monday CRM has no native geolocation column type for map visualization — for mapping visualization of serve locations, a third-party integration like Maplytics can plot these text coordinates on a map widget after migration.

ServeManager users (process servers, administrators, and billing staff) are mapped to monday CRM team members using email address matching as the primary key. Any unmatched users are flagged during the pre-migration audit for your admin to create or assign manually. Monday CRM permissions operate at the workspace level, so your admin configures board access after migration based on the role data extracted from ServeManager.