Migrate from Less Paper Co. to Freshsales

Less Paper Co. company stored as text, not a linked record

Less Paper Co. stores the company name as a free-text field on a contact rather than as a linked company record. When this text value does not resolve to an existing Account record in Freshsales, the Contact lands without an AccountId and is flagged for manual review. FlitStack AI flags every unlinked contact before migration commits, but the resolution — creating the Account first or reassigning the Contact — requires a decision from your team.

Work order status values do not map to Freshsales deal stages

Freshsales deal stages (Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost) are designed for sales pipeline progression. Less Paper Co. work order statuses (Scheduled, In Progress, On Hold, Completed) are service-job lifecycle values. These are fundamentally different concepts. FlitStack AI maps work order status to a custom pick-list field on the Deal (Work_Order_Status__c) rather than the native stage field. Your team must agree on this mapping in the migration plan before data lands.

Scheduling, dispatch, and inventory have no Freshsales equivalent

Freshsales has no native scheduling, dispatch, or field inventory object. Less Paper Co. scheduling records — appointment times, technician assignments, route information, parts availability, and payment collection status — cannot be represented in Freshsales' CRM model. These records do not migrate. Your team needs a field service management tool post-migration to continue managing scheduling and dispatch operations. FlitStack can export the scheduling and dispatch data as a CSV file so your team can import it into a dedicated field service platform such as ServiceTitan, Jobber, or Freshsales’ Freshservice. The exported file preserves appointment times, technician IDs, route sequences, and parts used, allowing a smooth handoff without loss of operational history.

Freshsales API rate limits cap bulk import throughput

Freshsales rate-limits the CRM API at approximately 100 requests per minute per app integration. Large migrations with 50,000+ records require chunked import batches with retry logic. FlitStack AI sequences the load in batches and implements exponential backoff on 429 responses. The cutover timeline extends proportionally for large datasets — plan for 5–10 days for datasets exceeding 200,000 records. The exact limit may vary by Freshsales plan tier, and higher tiers can increase the per‑minute allowance. FlitStack monitors 429 headers, adjusts batch sizes dynamically, and can throttle to stay within limits without causing failures. For large datasets, FlitStack schedules runs during off‑peak hours to maximize throughput.

Work order line items collapse to custom fields or notes

Less Paper Co. work orders store line items — parts, labor rates, material costs, and quantities — as structured rows. Freshsales Deals do not have a native line-item sub-object at the CRM tier (Freshsales Products handle pricing for quotes, not for work order cost tracking). FlitStack AI stores line item summaries as a custom long-text field (Parts_List__c) and individual part names as a multi-select field. Detailed cost breakdowns per line item require a custom Freshsales module at the Enterprise tier.