Migrate from ServeManager to Odoo CRM

ServeManager Jobs map 1:1 to Odoo crm.lead records. The job's service type, party type, court jurisdiction, and serve deadline migrate as custom selection fields on crm.lead. Odoo's lead_rating and priority fields provide a close analogue to ServeManager's job urgency flags. The crm.lead type field is set to 'opportunity' for active jobs and 'lead' for incoming service requests.

Each ServeManager Attempt is a first-class record with timestamp, GPS, photo, and signature. Odoo has no native attempt object, so FlitStack writes Attempts as mail.activity records (activity_type='attempt', summary=attempt_number) linked to the parent crm.lead. GPS lat/lng writes to x_gps_latitude and x_gps_longitude custom float fields on the lead. Photos and signatures migrate as ir.attachment records linked to the lead.

ServeManager Companies (law firms, process servers, clients) map to Odoo res.partner records. Company name maps to partner name, address fields map directly, phone maps to phone, and email maps to email. Odoo's is_company flag is set True for law firms and process-server accounts, and False for individual contacts stored under a company.

ServeManager client contacts (the person or entity being served, plus law-firm representatives) map to res.partner child records linked to the parent company partner via parent_id. Contact name, phone, email, and address migrate directly. For served parties without an existing Company record in ServeManager, a placeholder res.partner is created.

ServeManager job status values (open, completed, bounced, returned, paid) map to Odoo crm.stage pipeline stages. FlitStack creates a ServeManager-style pipeline in Odoo with stages that mirror the source status vocabulary. Stage-entered timestamps are preserved via Odoo's date_last_stage_update field, and an x_original_status__c custom field preserves the source value for reconciliation.

ServeManager invoices have no Odoo CRM equivalent. FlitStack exports all Invoice records as CSV (invoice_number, amount, status, Stripe charge ID, server_payable_amount) for import into Odoo Accounting. The invoice attachment PDFs are stored as ir.attachment records and can be linked to account.move records manually post-import or via Odoo Accounting's document management.

ServeManager Payment records (Stripe transactions, cash payments, refunds) are exported as CSV for Odoo Accounting import. Payment method, amount, date, and linked invoice number are included in the export along with the Stripe charge identifier for reconciliation against bank statements. Payment-to-invoice matching is done in Odoo Accounting after the CSV import using the invoice_number column to link each payment to its corresponding account.move record.

ServeManager tracks per-server compensation owed for completed jobs. FlitStack creates x_server_payable_amount on the process server's res.partner record and maps the current outstanding balance. Odoo's account_payable model can reconcile this, but a custom float field preserves the ServeManager-native figure for audit continuity.

ServeManager custom fields on Jobs (e.g., court_division, service_type_code, case_number) are discovered via CSV column inspection before migration. Each custom field creates a corresponding x_fieldname custom field on crm.lead via Odoo's ir.model.fields or Studio. Field type mapping follows Odoo's type system: selection for pick-lists, char for text, float for numeric GPS or monetary values.

ServeManager documents attached to Jobs (affidavits, proof-of-service PDFs, uploaded forms) are downloaded and re-uploaded as ir.attachment records linked to the parent crm.lead. Odoo's attachment storage limit (default 25MB per file) applies; larger affidavit files are flagged before migration so the team can archive them externally and link by URL.

ServeManager user accounts (process servers, admin users) are mapped to Odoo res.users by email match. Unmatched users are flagged pre-migration. Odoo's res.users do not store serve-specific data — the process server's active job count and performance metrics are stored on res.partner as custom fields (x_active_jobs, x_completion_rate) after migration.

ServeManager allows law firms to invite clients to a portal view for job tracking. Odoo has a portal module that grants external access to res.partner records, but the ServeManager portal data (client-viewed status history, client-commented attempts) does not map to a standard Odoo object. We export this as JSON and note it as a manual rebuild item for Odoo portal configuration.