Migrate from Drivecentric to Twenty CRM

DriveCentric contacts map directly to Twenty People. Phone, email, name, address, and job title translate 1:1. The original DriveCentric createdate is preserved as Original_Create_Date__c for reporting continuity. Contact owner resolves by email match to a Twenty WorkspaceMember; unmatched owners are flagged before import. Contacts without a linked company land as standalone People records, while those with a company link are associated via companyId after Companies load.

DriveCentric dealerships and company accounts map to Twenty Companies. Company name, address, industry, and employee count translate 1:1. Parent–child company hierarchies in DriveCentric map to Twenty's company relations field. Multi-contact accounts generate one Companies record with multiple linked People records.

DriveCentric deals with automotive bucket stages (New, Working, Presented, Negotiating, Sold) map to Twenty Opportunities. Each DriveCentric pipeline bucket becomes a custom Opportunity stage pick-list value in Twenty. Stage-enter timestamps migrate as custom datetime fields for reporting continuity. Probability and forecast category require Salesforce-style reapplication in Twenty's pipeline view.

DriveCentric's vehicle record has no Twenty native equivalent. We create a Vehicle custom object with fields for VIN, year, make, model, stock number, and sale status. Vehicle records link to People (buyer/seller) and Opportunity (deal) via relation fields. Your admin creates the custom object in Settings → Data Model before migration runs.

DriveCentric auto-generates tasks on leads (Day 2, 3, 4, 5, 7, 12, 13, 15 follow-ups per Reddit report). These migrate as Twenty Tasks with the original due date and assignee preserved. Task type is set to 'Follow-up' and linked to the parent People record. You decide post-migration whether to keep or archive these tasks.

DriveCentric call logs, emails, and text threads attach to the contact record. These migrate as Twenty Notes with original timestamp, author, and type field set to 'Call', 'Email', or 'Text'. Note body preserves the original content. Attachments re-upload to Twenty's file storage.

DriveCentric tracks lead source (website, third-party, OEM referral) as a contact property. Twenty has no native lead source field on People. We create a 'Lead_Source__c' select field with source values mapped value-by-value. The admin configures options in Twenty's field settings before import.

DriveCentric alerts salespeople when customers visit service. This automotive feature has no Twenty equivalent. A custom object 'ServiceReminder' with fields for customer link, vehicle link, service date, and reminder date is created. Your admin rebuilds the notification trigger in Twenty's workflow builder using date-based triggers.

DriveCentric Enterprise supports custom objects (F&I products, service contracts). These map 1:1 to Twenty custom objects. N:N relationships in DriveCentric require junction objects in Twenty since Twenty's relation model is one-to-many by default. We document the junction mapping in the migration plan.

DriveCentric owner IDs resolve by email to Twenty WorkspaceMember records. Unmatched owners are flagged before migration—your team creates Twenty accounts for them first, or records assign to a fallback owner. Twenty's permissions model (11 permission groups) requires post-migration profile assignment.

DriveCentric files attached to contacts, companies, and deals are re‑uploaded to Twenty Files, preserving filename and upload date. File size limits and handling follow Twenty's restrictions; files over limit are flagged for chunked import. Exports such as roofsheet scans or deal jackets that exceed size threshold may need to be split before upload. FlitStack supplies a file audit report listing each attachment and its size to help plan the upload.

DriveCentric Automation Hub sequences (automated follow-up, AI nurture, OEM campaign triggers) do not migrate. These are process logic, not data. FlitStack exports the sequence definitions as a JSON rebuild reference. Twenty's workflow builder recreates trigger-based automations using field-change and time-delay conditions.