Migrate from OptimoRoute to Nutshell

Nutshell has no native routing or route-optimization object

OptimoRoute's core data model revolves around routes, stops, time windows, driver constraints, and vehicle load capacities. Nutshell models Deals as sales or service records without any routing capability. Every OptimoRoute routing attribute — route name, stop sequence, planned vs. actual distance, driver skill constraints, vehicle capacity flags, and commercial routing restrictions — must be decomposed into Nutshell custom fields on Deals or People. This means OptimoRoute's optimization engine outputs cannot be replicated in Nutshell; they become reference data on the deal record. FlitStack AI handles this decomposition but your team should understand that Nutshell will display routing metadata, not drive routing decisions.

OptimoRoute API concurrency limit of 5 affects export speed

OptimoRoute's Web Service API caps concurrent requests at 5 per account or IP address. For large fleets exporting thousands of orders, drivers, and vehicles, this throttles the initial data pull. FlitStack AI paces exports with retry logic and batches requests to stay within the 5-concurrent limit. The migration timeline for large datasets accounts for this pacing. If your OptimoRoute plan includes the custom API tier, the limit may be adjustable — confirm with OptimoRoute support before migration planning.

OptimoRoute customer address storage can duplicate across orders

OptimoRoute stores addresses at the order level rather than maintaining a normalized customer address record. A customer who receives deliveries at the same address across 50 orders may have 50 slightly different address strings in OptimoRoute. When these map to Nutshell People (which have a single address field per type), we apply address normalization — standardizing street abbreviations, postal codes, and unit numbers — and flag duplicates for your team to review before the full migration commits. Without this step, Nutshell People records would contain fragmented address history that breaks reporting filters.

Multi-select custom order fields in OptimoRoute require manual conversion

Nutshell's custom field choices are single-select only. OptimoRoute's custom order fields support single-select pick-lists with multiple options per field, but Nutshell does not natively support a multi-select custom field type on Deals or People. If OptimoRoute custom fields use multi-select patterns — for example, a 'service_type' field where an order can have both 'Installation' and 'Repair' selected — those must be converted to a semicolon-delimited text field in Nutshell or decomposed into separate single-select fields per value. FlitStack AI surfaces these cases in the pre-migration field audit so the conversion logic is agreed upon before data moves.

OptimoRoute driver-app accounts and dispatcher accounts map to different Nutshell user types

OptimoRoute distinguishes between dispatcher accounts (who plan routes) and driver-app accounts (who execute them). Nutshell's user licensing model is per CRM user seat. If your OptimoRoute plan includes driver-app users who should not have CRM access in Nutshell, we create them as Nutshell People records (Driver type) without assigning a Nutshell user license. Dispatcher accounts that need CRM access map 1:1 to Nutshell Users by email. This split prevents you from paying for unnecessary Nutshell seats for drivers who only interact with the routing software, but it means driver-app users cannot log into Nutshell without a seat upgrade.