Migrate from StrategicERP to Freshsales

StrategicERP companies map directly to Freshsales Accounts. The company name, address, industry, and employee count transfer as standard Account fields. Parent-company hierarchies in StrategicERP map via Freshsales's Account hierarchy feature. Companies without a primary contact require an Account record with a placeholder contact.

StrategicERP records that have not been converted to active customers are split to Freshsales Leads. If StrategicERP stores a 'Status' field with 'Lead' or 'Prospect' values, those records route to Freshsales Lead; otherwise, they default to Lead based on missing purchase data. Active customer records route to Account/Contact. This split ensures early‑stage prospects populate the CRM funnel correctly.

StrategicERP contacts with an associated company map to Freshsales Contacts linked to the corresponding Account. Freshsales requires a valid email address — contacts without email are flagged and require manual resolution or a default placeholder email before migration. The placeholder ensures API acceptance while allowing admins to review and supply a real email later. All other fields (phone, job title, address) transfer directly.

StrategicERP contacts that lack a confirmed purchase or project assignment map to Freshsales Leads. Name, phone, job title, and email transfer directly; any additional contact details are preserved as custom fields on the Lead. The Lead Source field defaults to 'Other' unless StrategicERP captures a referral origin, in which case that value is used to populate the field. This ensures early‑stage contacts enter the CRM funnel with accurate source attribution.

StrategicERP's sales records (quotes, won/lost deals) map to Freshsales Deals. Deal name, amount, stage, expected close date, and owner transfer directly; probability and any custom fields are also migrated. Stage values require value mapping between StrategicERP's stage labels and Freshsales pipeline stage names, ensuring each deal lands in the correct pipeline stage. Lost deals retain their original loss reason as a custom field for post‑mortem analysis.

StrategicERP supports multiple pipelines for different project types. Each pipeline maps to a Freshsales Deal Pipeline. Stage names and probabilities are mapped value-by-value. If StrategicERP uses a single pipeline, a default Freshsales pipeline is created and all deals assigned to it.

StrategicERP's core Project object has no direct Freshsales equivalent. For sales-driven projects (client-facing deliverables), we map to a Freshsales Deal with custom fields for project code, project stage, and estimated completion date. For operational projects, we create a Freshsales Custom Module with fields for cost budget, actual cost, and status.

StrategicERP activity logs (call logs, email records, meeting notes) map to Freshsales Sales Activities. Each activity preserves the original timestamp, owner, and linked contact or deal; the subject line becomes the activity title and any notes are stored in the body field. Activity type (call, email, meeting) maps to Freshsales's Sales Activity type field, ensuring correct categorization. If a linked contact or deal is absent, the activity is attached to the nearest parent record to maintain context.

StrategicERP user accounts are matched to Freshsales users by email address. The migration engine performs a case‑insensitive match; if multiple Freshsales users share the same email (rare), the first active user is selected. Unmatched owners are flagged before migration — teams either invite the user to Freshsales or assign records to a fallback owner selected by your admin. This prevents orphaned records and ensures that all Deal and Activity ownership is assigned from day one.

StrategicERP custom properties — cost codes, unit types, project stages, compliance flags — map to Freshsales custom fields on the appropriate object (Account, Contact, Deal) or a custom module. Freshsales custom fields must be created before the migration run; we deliver the schema plan upfront so your admin can provision them.

Files attached to StrategicERP records (drawings, contracts, photos) are downloaded and re‑uploaded to Freshsales as file attachments on the record, preserving the file name and timestamp. The migration engine maps each file to the target object using the parent record identifier. File size limits of the Freshsales plan apply (Growth: 2 GB/user; Pro: 5 GB/user; Enterprise: 100 GB/user); any file exceeding the limit is flagged for handling, ensuring documentation is available after cut‑over.

StrategicERP stores project revenue, costs, and margins that have no Freshsales native equivalent. We create custom number fields (Projected_Revenue__c, Actual_Cost__c, Profit_Margin__c) on the Account or Deal record. These fields are available for reporting in Freshsales dashboards but do not drive Freshsales automation natively.