Migrate from Streamleader to Acumatica

Streamleader contacts map to Acumatica Customers with Contact sub-records. The primary company association becomes Customer.Class or a custom UDF. Secondary company associations become Customer Contact Relations in Acumatica. Contacts without a company link create a Customer with no associated account.

Streamleader company name becomes Customer.CustomerID and CustomerName fields. Company address becomes the default Customer address with a corresponding Location record. Multiple distinct locations in Streamleader map to separate Customer Locations in Acumatica, each with unique address and contact details.

Streamleader deals that represent a one-time sale route to Acumatica Opportunities in the CRM module. Deals representing a project or retainer with task-level billing route to Project Tasks under a Project. The routing split is based on deal type metadata or a customer-provided classification rule.

Streamleader pipeline defines stages and probabilities for deal progression. For Opportunity-routed deals, the pipeline transforms into an Acumatica Sales Process tied to Sales Orders. For Project-routed deals, the pipeline becomes Project Template phases with task statuses mapped from Streamleader stage names.

Streamleader calls and emails migrate as Acumatica Activities with Type = Call or Email respectively. Meetings migrate as Acumatica Events preserving original start and end times. Owner and timestamp metadata are preserved during migration. Emails that represent support requests can optionally route to Cases based on Streamleader activity type.

Streamleader notes attach to the parent record via NoteID reference. Rich-text HTML formatting is preserved intact when stored in Acumatica Notes. Inline images embedded in Streamleader notes are extracted, downloaded, and re-uploaded as separate file attachments in Acumatica.

Streamleader file attachments re-upload to Acumatica Files attached to the same entity via NoteID. File size limits apply with a default of 25MB per file in Acumatica. Files without a parent record link are attached to the primary Customer record as a fallback location.

Streamleader custom objects map to Acumatica custom tables (DACs) created within the Customization Project framework. N:N associations present in Streamleader require junction tables in Acumatica to preserve many-to-many relationships. We deliver the complete DAC schema and relationship diagram before migration runs.

Streamleader owner IDs resolve by matching email addresses against Acumatica users in the system. Users must exist in Acumatica before migration begins — we flag any unmatched owners and let the customer decide between inviting them as new users or assigning their records to a fallback owner.

Streamleader workflows do not migrate directly due to architectural differences. We export workflow definitions as JSON including trigger conditions, action steps, and filter logic. Email notification templates export separately as HTML files. An Acumatica functional consultant uses this as a rebuild reference for Business Events, Screen-Based automations, or Generic Inquiry alerts.

Streamleader reports and dashboards do not migrate structurally, though the underlying data transfers successfully. We export the report field list and filter logic as a reference document for rebuild efforts. The Acumatica rebuild uses Generic Inquiry (saved search equivalent) or Report Designer depending on report complexity.

Streamleader leads map directly to Acumatica Prospects in the system. Prospects can be converted to Customers through Acumatica's standard conversion workflow. Lead status and score values from Streamleader migrate as UDFs on the Prospect entity for continued lead management.