Migrate from WennSoft to Freshsales

WennSoft Customer records map directly to Freshsales Accounts (business entity). Primary contact within the Customer record maps to a Freshsales Contact linked via AccountId lookup. Additional contact roles within WennSoft Customer are surfaced as Freshsales Contact records under the same Account.

WennSoft Location records attach to Customers and store site-level addresses, cross-references, and notes. FlitStack migrates the primary location address into Freshsales Account address fields and secondary locations into custom address fields on the Account or linked Contact records for multi-site visibility.

WennSoft Equipment records hold serial numbers, model info, install dates, and maintenance history. These map to Freshsales Products (Name, SKU, unit_price) with custom fields capturing original Equipment ID, install_date, and warranty_expiry. On Enterprise, a custom Equipment module stores full maintenance history as related records.

WennSoft Service Call records represent individual field visits tied to customers and equipment. FlitStack creates a Freshsales Deal per customer (or per contract) and writes Service Call details — call number, status, call_type, problem_description — into custom fields on the Deal. Each individual visit can surface as a linked Task.

WennSoft Work Orders are detailed job documents with line items, labor hours, and materials. FlitStack maps Work Order summary data (work_order_number, scheduled_date, status, total_cost) to custom fields on a Freshsales Deal. Line-item detail can map to Deal Products if the structure parallels Freshsales product-line model, or remain in a custom Work_Order_Detail__c field as JSON for reference.

WennSoft Employee records are internal users who own Service Calls and Work Orders. FlitStack resolves each Employee by email address against Freshsales Users and creates a Contact record for employees who are also customer contacts. Unresolved employees are flagged for admin review before migration.

WennSoft Time Entries track labor hours against Work Orders. FlitStack maps each time_entry record to a Freshsales Task with custom fields capturing hours_worked, labor_rate, and billable_amount. Original timestamps and technician ID are preserved in custom datetime fields for reporting continuity in Freshsales. Billable vs. non-billable flags map to Task status or custom pick-list fields to maintain time-tracking categorization across the migration.

WennSoft Invoice records close Work Orders and record billing. FlitStack migrates invoice_number, invoice_date, total_amount, and payment_status into custom fields on the parent Freshsales Deal. Financial transaction history is preserved as a reference-only custom field since Freshsales is not a billing system.

WennSoft supports custom fields on most record types via GP's Dexterity-based schema. FlitStack creates equivalent custom fields on Freshsales CRM objects — Account, Contact, Deal, Product — using the Enterprise custom-field allowance or the 2-field limit on lower plans, prioritizing the most business-critical custom properties.

WennSoft stores document attachments on Service Calls, Work Orders, and Equipment records. FlitStack re-uploads each file to Freshsales Files linked to the corresponding Account, Contact, Deal, or Product record. File size limits (Freshsales default 25MB per file) are respected; larger files are flagged for manual handling.

If WennSoft stores prospect or sales lead records in a custom GP table, FlitStack maps them to Freshsales Leads with standard fields (name, email, phone, status, source) and preserves any custom fields. Leads without an assigned customer become unassigned Freshsales Leads for follow-up.

WennSoft inventory parts used in Work Orders map to Freshsales Products with Name, SKU, unit_price, and stock_quantity fields. Part descriptions map to Product Description. Freshsales does not have native inventory management — parts usage on Work Orders is tracked via custom fields or Deal Products.