Migrate from Drivecentric to Nutshell

DriveCentric Contacts map directly to Nutshell People. Nutshell People store name, email, phone, address, title, and owner. The mapping preserves the contact's original create date as a custom field since Nutshell's created_at timestamp reflects the migration import date rather than the original record creation date.

DriveCentric Companies map to Nutshell Companies. Dealership groups operating multiple rooftops under a single ownership entity use DriveCentric's parent-child company hierarchy to model the same structure in Nutshell. Each individual rooftop location is created as its own Nutshell Company, and the parent ownership organization is set as the parent company via Nutshell's parent_company reference. This preserves the full dealership network structure in the destination system.

DriveCentric Deals map to Nutshell Deals carrying deal name, value, stage, and close date. Nutshell's Deal object does not support custom fields — automotive-specific deal data (trade-in value, after-market products, F&I products sold) must be stored as custom fields on the associated Person or Company record instead.

DriveCentric pipelines (New, Working, Closing, Won, Lost) map to Nutshell Pipelines. If DriveCentric has multiple pipelines (e.g., separate sales vs. service pipelines), Nutshell's Pro/Business plan supports multiple pipelines — Starter/Foundation uses a single pipeline. We assess the pipeline count against the target Nutshell plan during scoping.

Each DriveCentric pipeline stage name (Lead, Demo, Proposal, Negotiation, Closed Won, Closed Lost) maps value-by-value to a Nutshell Stage. Stage probability defaults to 50% in Nutshell if no probability data exists in DriveCentric. Stage entry dates are preserved as custom datetime fields on the Deal record.

DriveCentric custom fields on Contacts and Companies (trade-in vehicle details, credit application status, vehicle interest, service history) have no Nutshell native equivalent. We create corresponding Nutshell custom fields on Person or Company before migration. Automotive fields that cannot be cleanly mapped to a Nutshell object are flagged in the migration plan for manual review.

DriveCentric's activity log (calls, emails, texts) maps to Nutshell Activities with the activity type preserved (call, email, chat). Original timestamps and owner attribution carry over. Nutshell's activity type field uses a controlled vocabulary — DriveCentric's text message activities map to Nutshell's 'Chat' type.

DriveCentric notes attach to contacts, companies, or deals. Notes migrate to Nutshell Notes preserving the body text, author, and creation timestamp. If DriveCentric stores notes in a rich-text format, we convert to plain text for Nutshell's note body field to avoid rendering issues.

DriveCentric owner IDs are resolved to Nutshell Users by email address match. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts for them first or assigns their records to a fallback Nutshell user. No record lands without a valid Nutshell owner assignment.

DriveCentric leads without a closed deal map to Nutshell Leads. Nutshell Leads are distinct from People — a lead can exist without a corresponding Person record. We map the lead name, contact info, source, status, and any custom fields. Once a lead converts to a deal in DriveCentric, the associated Person and Deal are migrated separately in Nutshell.

DriveCentric file attachments on records (vehicle photos, credit applications, deal documents) are downloaded and re-uploaded to Nutshell's file storage linked to the corresponding Person, Company, or Deal record. Nutshell's file size limits apply — files exceeding the limit are flagged for manual handling.

DriveCentric contact and deal tags (e.g., 'hot prospect', 'service customer', 'ev buyer') migrate to Nutshell Tags. Tags are preserved as-is — Nutshell's tag model supports multiple tags per record. DriveCentric's tag taxonomy is reviewed to avoid duplicates or inconsistent naming before migration.