Migrate from Drivecentric to monday CRM

DriveCentric automotive fields have no native monday CRM home — custom columns must be pre-created per board

Dealership-specific fields like trade_in_value, GAP_coverage, lien_holder, OEM_certification_level, and vehicle_VIN have no equivalent column type in monday CRM's base schema. Each field requires a custom column created manually (or via API) in monday CRM before the migration runs — otherwise those columns are absent and data lands in an unstructured text field. FlitStack delivers a column-setup specification listing every automotive custom field, its column type in monday CRM, and the target board, so your admin can provision columns in advance. Without pre-created columns, FlitStack falls back to text columns and flags them in the pre-migration diff report.

monday CRM API rate limits throttle bulk data ingestion at higher plan tiers — migrations may require batch pacing

monday CRM's API enforces a daily call limit: 1,000 calls/day on Basic/Standard, 10,000 on Pro (soft limit), and 25,000 on Enterprise. A DriveCentric export containing 20,000 deals plus 15,000 contacts exceeds the Standard daily limit when each record requires separate API calls for creation and column updates. FlitStack uses batch insertion where monday CRM's API supports it, but complex column updates on items require individual calls that count against the daily budget. We pace migrations to avoid DAILY_LIMIT_EXCEEDED errors and will pause and resume across day boundaries if the plan tier caps the run. The Enterprise plan's 25,000-call limit handles most dealership migrations without throttling.

DriveCentric lead-assignment and OEM routing rules cannot be transferred — they require rebuild in monday CRM automations

DriveCentric Automation Hub rules (round-robin lead distribution by team, OEM-specific routing based on vehicle type, BDC follow-up triggers) live in DriveCentric's automation engine and have no data representation in the export. monday CRM's automation system (recipes) operates at the board level with triggers like 'when status changes to X' or 'when item is created' — it does not have a native lead-assignment engine or sequence automation comparable to DriveCentric's routing logic. FlitStack exports DriveCentric automation definitions as plain-language rebuild documentation specifying the trigger, condition, and action for each rule, but the automations themselves must be manually reconstructed in monday CRM after data lands.

Vehicle-to-deal cross-object linkage requires monday CRM Connect Boards column — not auto-created on import

DriveCentric links vehicles to deals through a vehicle_id foreign key on the Deal object. monday CRM replicates this relationship using the Connect Boards column, which must be manually added to the Deals board and configured to link to the Inventory board before records migrate. If the Connect Boards column does not exist at migration time, vehicle IDs are stored as a text field on the deal item and flagged in the migration report for post-migration manual linking. FlitStack cannot auto-create monday CRM board-level relationship columns through the API without additional permissions — this step requires your monday CRM admin to configure the board structure in advance.

Activity history surfaces as monday CRM Updates rather than structured activity records — report continuity breaks without a custom date column

DriveCentric stores activity records (calls, emails, texts) with structured fields: activity_type, duration, outcome, owner, timestamp, and notes. monday CRM has no structured activity object — all engagement history becomes threaded Updates on the contact or deal item. The chronological sequence of interactions is preserved in the update order, but there is no dedicated activity log table to query for reporting. For teams relying on DriveCentric activity reports (average call duration by rep, email open rates), monday CRM requires a custom date column on every item capturing the last activity timestamp. FlitStack adds a Last_Activity_Date__c-equivalent date column to every migrated item to partially preserve reporting continuity.