Migrate from Route4Me to Freshsales

Route4Me is route optimization software, not a CRM — most entities have no Freshsales equivalent

Route4Me stores routes, stops, driver assignments, GPS tracks, and service-time windows as core platform entities. Freshsales has no native objects for any of these operational logistics concepts. We migrate the address book contacts and order records; everything else is excluded from the migration or preserved as reference-only custom fields on the linked Deal record. Before migration begins, confirm with your team which Route4Me fields represent customer data versus operational logistics data that should not populate a CRM environment.

Route4Me Custom Order Fields require pre-creation in Freshsales before migration writes data

Route4Me Custom Order Fields are defined per-account and attached to orders and addresses as a core part of the routing workflow. Freshsales custom fields are created per-module (Contact, Account, Deal) through Admin settings, which is a different architectural approach. We cannot write to a Freshsales custom field that does not exist in the target schema. We deliver a comprehensive schema setup plan listing every Route4Me custom field, its data type, and the exact Freshsales equivalent to create before the migration runs — covering checkbox, picklist, text, number, and date field types.

Route4Me address-to-company association is loose — company deduplication requires admin rules

Route4Me stores company_name as a free-text property on each address record, allowing inconsistent entry across records. The same company may appear under slight variations ('Acme Corp' vs 'Acme Corporation' vs 'Acme Corp.') creating duplicates if not normalized. We deduplicate by exact match first, then apply a fuzzy-match threshold for flagged review by your team. Your admin confirms the deduplication rule before migration so each unique company lands as one Freshsales Account with all related Contacts properly linked under that Account.

Route4Me driver and member records have no Freshsales user equivalent by default

Route4Me Members and Drivers are internal personnel within the routing platform and are not email-matched to CRM contacts by default design. We match Route4Me owner_email values to Freshsales users for Contact OwnerId population, but driver names attached to orders become reference text stored in Last_Driver__c on the Deal record. If your drivers also function as sales contacts in your organization, they should be imported from the Route4Me address book separately to avoid being treated as customers in Freshsales rather than internal team members.

Freshsales API rate limits vary by plan — large migrations require throughput planning

Freshsales API rate limits are 1,000 requests per hour on Growth, 2,000 on Garden, and 5,000 on Estate/Forest plans. Route4Me address book exports can reach tens of thousands of records. We pace the migration to stay within the target plan's rate limit, using batch writes and exponential backoff on 429 responses. Inform us of your Freshsales plan tier before the migration window so we can configure the correct throughput profile.