Migrate from PHP CRM to Nutshell

PHP CRM Contact records map to Nutshell People. Standard fields (name, email, phone, address) map directly. We extract every custom field present on Contact in the source deployment and map to Nutshell People custom fields or the Notes field for unstructured data. Contacts are imported after Companies to satisfy Nutshell's company association on People.

PHP CRM Company records map 1:1 to Nutshell Company. Company name, domain, address, and industry fields migrate directly. Nutshell's People-Company association is resolved by matching the domain or company name from the source Contact record. We import Companies first as the parent entity before any associated People records.

PHP CRM Deals map to Nutshell Leads. Deal value, stage, expected close date, and owner assignment transfer to the Lead's monetary value, status, expected close, and owner fields. We enumerate the actual pipeline and stage values present in the source PHP CRM deployment and map them to Nutshell's Lead status values, flagging any stages with no direct Nutshell equivalent for customer review.

PHP CRM's custom pipeline definitions map to Nutshell's Lead status values and a single lead pipeline. Since Nutshell organizes around People, Companies, and Leads rather than multiple deal pipelines, we flatten the source pipeline structure into a single Nutshell Lead stream and preserve the original pipeline name in a custom field for reporting.

PHP CRM stage names and order vary by deployment configuration. We extract the full stage list from the source instance, map each stage to a Nutshell Lead status value, and flag any stages with no direct equivalent. The customer reviews stage mapping during discovery before any data moves.

PHP CRM Tasks map to Nutshell Tasks. Due date, assignee, status, and linked entity (Person, Company, Deal/Lead) transfer directly. Entity linkage in Nutshell uses the Nutshell-assigned ID for the target record, which we resolve after parent record migration completes. Task status values are mapped from PHP CRM's internal status codes to Nutshell's open/closed states.

PHP CRM Notes attach free-text content to any entity (Contact, Company, Deal). Notes migrate as Nutshell Note records linked via the target entity's ID after parent resolution. Rich text formatting is preserved where PHP CRM stores it as HTML.

PHP CRM Activity records (calls, emails, meetings) vary in schema by deployment. We enumerate the actual activity fields present in the source instance and map call logs, email records, and meeting entries to Nutshell's activity timeline. Nutshell's activity tracking uses a linked log structure per Person or Company. The customer chooses whether to import the full activity history or the most recent 12-24 months based on data volume.

PHP CRM allows user-defined custom fields on all standard objects with no standardized taxonomy. We run a mandatory discovery phase that enumerates every custom field present across all objects in the source deployment. Each custom field is typed (text, number, date, dropdown, checkbox) and mapped to the equivalent Nutshell custom field type. Nutshell's custom field limit varies by plan (Foundation has a lower ceiling; Pro and above support more). We flag any fields that would exceed Nutshell's tier ceiling for customer review.

PHP CRM User records (owners assigned to Deals and Tasks) map to Nutshell Users by email matching. We extract every distinct owner referenced on records and attempt email-based lookup in the Nutshell destination. Users without a match enter a reconciliation queue for the customer to provision in Nutshell before record import resumes.

PHP CRM tags label records for segmentation and vary per instance. We extract the full tag vocabulary and map to Nutshell Tags on People, Companies, and Leads. The customer reviews the tag taxonomy during discovery to confirm coverage.

PHP CRM stores file attachments on the local filesystem or cloud storage path, not through a documented API endpoint. We export attachments to a local directory for customer review and advise re-uploading via Nutshell's bulk file tools or manual attachment flow post-migration. This is a manual step outside the automated migration scope.