Migrate from Comarch Field Service Management to Nutshell

Work order records have no direct Nutshell equivalent — Nutshell has no work order, task-assignment, or dispatch object. FlitStack AI migrates the service request description, ID, status, priority, and SLA deadline into Person custom fields so the record context is preserved even though it cannot drive Nutshell workflows.

Comarch customer profiles — name, phone, email, role, contact method — map 1:1 to Nutshell Person records. FlitStack resolves each Comarch customer to a Nutshell Person by email match. Customers without an email receive a generated placeholder address flagged for manual review before the full migration runs.

Comarch commercial customers stored with an organization type map to Nutshell Company records. The Company Name, domain, industry, and address fields map directly. Comarch's parent-customer hierarchy maps to Nutshell's Parent Company field if your Nutshell account has the hierarchical company structure enabled.

Technicians in Comarch FSM are operational employees, not sales contacts. FlitStack maps technicians to Nutshell Person records with a custom Technician_Role__c flag set to TRUE. If technicians also act as Nutshell users, owner resolution by email links their Person record to the corresponding Nutshell User. Scheduling and dispatch data does not migrate — those are FSM constructs with no Nutshell equivalent.

Comarch service location addresses map to Nutshell's address fields on the linked Company or Person record. Multi-site Comarch customers with multiple service locations create multiple address entries in Nutshell linked to the same Company. Address normalization runs before migration to ensure consistent formatting in Nutshell's structured address fields.

Comarch service request status-change history is a timeline of FSM events. FlitStack translates each status transition into a Nutshell Task record with a custom Status_History__c field holding the original Comarch status value and timestamp. This preserves the service history as an activity log on the Person or Company record without relying on Nutshell's native workflow capabilities.

Comarch asset records track equipment linked to service locations — serial numbers, installed date, maintenance schedule, IoT sensor readings. Nutshell has no asset management object. FlitStack migrates the asset ID, description, and last-service date into Company custom fields for reference. Live IoT sensor data and maintenance schedules do not transfer and must be archived externally.

Comarch parts inventory and bill-of-materials data maps to no Nutshell object — Nutshell is a CRM, not an inventory or procurement system. FlitStack preserves the parts reference data as a custom Note attached to the relevant Company record so the part list is not deleted, though it cannot drive Nutshell stock or fulfillment workflows.

Comarch user-defined fields on any object that have no Nutshell standard equivalent are created as Nutshell custom fields under the matching record type (Person, Company, or Lead). FlitStack pre-creates the field schema in your Nutshell account before the migration run and maps values field-by-field. Field type is matched as closely as possible — pick-lists to pick-lists, dates to dates, text to text.

Documents and files attached to Comarch service requests or customer records are downloaded and re-uploaded to Nutshell as Files attached to the corresponding Person or Company record. Nutshell's 25MB per-file limit is enforced — files exceeding this are flagged before the migration and handled per your instructions.

Comarch user accounts for administrators and service managers are resolved by email match to existing Nutshell users. Unmatched accounts are flagged before migration — your team either creates the Nutshell user first or assigns their records to a fallback owner. Nutshell's role and permission model is destination-side schema configuration and is not migrated from Comarch.