Migrate from Assembly Neos to Salesforce Sales Cloud

Neos clients map directly to Salesforce Contacts. Each client gets a Contact record with name, email, phone, address, and role fields populated from Neos client properties. Client create dates and modified dates preserved as custom fields since Salesforce CreatedDate reflects migration time.

Neos opposing parties may be individuals or organizations. When an opposing party is an organization, we create both an Account (holding the organization name) and a Contact (for opposing counsel or party representative). Individual opposing parties map to standalone Contacts without Account linkage. This two-step mapping ensures organizational hierarchy is maintained while preserving individual party details.

Neos insurance carrier records map directly to Salesforce Accounts. Carrier name, contact information, and policy numbers transfer to Account fields. Carrier classification (health, auto, liability) is stored as an Industry pick-list value or a custom field depending on the specific categorization your firm uses.

Neos medical provider records map to Salesforce Accounts with provider name, specialty, address, and contact information populating Account fields. A custom field flags the Account as a medical provider type for reporting segmentation and filtering across your case portfolio.

Neos matters map to Salesforce Cases, but legal case data requires extensive custom field configuration. Case number becomes Case Number, case type (PI, family, criminal) maps to a custom Case_Type__c pick-list, and case status (active, closed, pending) maps to Status. Jurisdiction, venue, and assigned judge become custom fields.

Neos party roles including plaintiff, defendant, witness, and expert map to Salesforce Contact Roles on the Case object. Custom role values require the Salesforce admin to pre-create corresponding Contact Role type values before migration runs.

Neos calendar entries including court dates, filing deadlines, and depositions map to Salesforce Events. Event start and end times are preserved, the subject line populates from Neos event title, and the related Case links via WhatId for relationship tracking.

Neos task items including to-do items, reminders, and follow-ups map to Salesforce Tasks. Subject, status, priority, and due date transfer directly. Task owner resolves by email matching to Salesforce users for proper assignment accountability.

Neos documents attached to cases are downloaded and re-uploaded to Salesforce Files. Files link to the corresponding Case record via ContentDocumentLink. The 25MB per file size limit is enforced; files exceeding this threshold require chunking or SharePoint migration as an alternative.

Neos time entries and expenses have no direct Salesforce equivalent. We create a Billable_Entry__c custom object with fields for hours, rate, expense amount, date, and linked Case. Your billing team maps this to QuickBooks or a legal billing tool post-migration.

Neos custom fields on cases such as lien holder, SOP date, adjuster claim number, and damages sought require corresponding Salesforce custom fields on the Case object. Custom pick-lists need value-by-value mapping when source values differ from Salesforce defaults.

Neos workflows for conflict checks, intake checklists, and deadline reminders have no Salesforce native equivalent. We export workflow definitions as JSON documentation for your Salesforce admin to reference during Flow reconstruction. Active automation transfer is not possible with current tools.