Migrate your Assembly Neos data

Matters is the core case container in Neos. Each Matter supports configurable case types, customizable layouts, and stage assignments. We preserve the full Matter hierarchy including related Contacts, Documents, Tasks, and Calendars during export and map stage names to equivalent destination statuses.

Contacts represent clients, opposing parties, witnesses, and other parties. We export all Contact fields including addresses, phone numbers, email addresses, and any custom contact properties. Related Contacts are linked to the parent Matter during migration.

Neos stores documents under the Docs tab with template generation capabilities. Premium and Pro tiers make PDFs text-searchable via OCR. We export documents with their metadata, version history where accessible, and note the OCR status of each file. Document folder hierarchy must be recreated at the destination.

Tasks are created per Matter with checklists and due dates. Custom checklist items per case type are supported. We export tasks with their assignees, due dates, completion status, and checklist structure, but custom task templates require field-level mapping to destination equivalents.

Neos provides shared firm calendars integrated with Microsoft 365. Calendar events are linked to Matters and Contacts. We export events with dates, times, attendees, and Matter associations, noting that Google Calendar integration requires reconnection in the destination platform.

Neos generates bills and invoices linked to Matters with line items, payments, and trust accounting. We export invoice data, payment history, and outstanding balances. Trust account transactions require careful mapping as Neos handles these separately from general billing.

Time entries record billable and non-billable hours against Matters. We export entry dates, durations, descriptions, billing rates, and Matter associations. Timekeeper assignments are preserved as user references in the export.

Neos supports custom fields on Matters, Contacts, and other objects. We export custom field definitions and values, noting that custom fields created post-migration in Neos may require redefinition in the destination system depending on field type compatibility.

Neos enables custom workflows based on case types and milestones. Automation rules, triggered actions, and workflow templates are exported where the API exposes them. Complex workflow logic may require manual recreation at the destination.

Neos integrates with QuickBooks, DocuSign, RingCentral, and Microsoft Office 365. We list active integrations during scoping and flag those requiring reconfiguration or re-authentication in the destination environment. API-based integrations (Zapier, RingCentral) may need webhook re-registration.

Notes attached to Matters or Contacts are exported as plain text or formatted content depending on storage format. We preserve note timestamps and author information. Notes containing sensitive data are flagged for redaction review during scoping.

Tags and labels used for Matter and Contact categorization are exported with their associations. Destination platforms handle tags differently, so we map tag values to equivalent labeling systems (categories, labels, custom properties) during field mapping.