Migrate from Estimate Rocket to Nutshell

Estimate Rocket client records (name, email, phone, address) map directly to Nutshell Person records. The client record also carries the company name which FlitStack extracts to create a linked Nutshell Company record first, then links the Person to it via the account lookup.

Estimate Rocket does not have a separate Company object — company information lives inside the Client record as a text name field. FlitStack extracts the company name, deduplicates across all client records sharing the same name, and creates a single Nutshell Company per unique name, then links all associated Person records to it.

Each Estimate Rocket Project becomes a Nutshell Deal. The Project name maps to Deal name; Project status (Active, Won, Lost, Archived) maps to Nutshell's Deal status. Original project create date is preserved as a custom field since Nutshell Deals track created date differently.

Estimate Rocket Estimates are child records of Projects. FlitStack merges the Estimate total amount into the parent Project's Nutshell Deal Amount field. If a Project has multiple Estimates (initial, revision), the most recent approved estimate amount is used as the primary Deal amount, and earlier estimate totals are preserved as custom fields.

Estimate Rocket line items (name, quantity, unit price, unit cost, section, type) have no direct Nutshell equivalent. FlitStack creates custom fields on the Nutshell Deal — Line_Item_Summary__c stores a text summary of the top line items; individual material and labor totals go into Material_Total__c and Labor_Total__c custom number fields.

Work Orders in Estimate Rocket represent scheduled execution of an approved estimate. FlitStack maps the Work Order status to a Nutshell Deal stage change (e.g., 'Work Ordered' → Nutshell stage 'Negotiation') and creates a linked Activity note capturing the Work Order description and assigned technician.

Estimate Rocket Employees with estimator or admin roles map to Nutshell internal users by email match. FlitStack resolves each Estimate Rocket owner_id to the corresponding Nutshell user. Field users (clock-only access) have no Nutshell equivalent — their names are preserved in activity logs but they do not become Nutshell users.

Estimate Rocket Schedule entries (appointment time, assigned employee, related project) map to Nutshell Activities. FlitStack preserves the original start/end datetime and links each Activity to the parent Project's Nutshell Deal. All-day events and task-type schedule entries map to Nutshell Tasks with the All-Day flag set.

Estimate Rocket Follow-Up Campaigns are email automation series triggered on project lifecycle events. Nutshell Sequences provide equivalent automation on Deal stage and lead status changes but are rebuilt manually. FlitStack exports the campaign definition (trigger event, step sequence, delay days, email body) as a JSON reference document for Nutshell admin to rebuild.

Estimate Rocket Invoices carry a status (Sent, Paid, Overdue, Void) and payment info. FlitStack maps invoice status to a custom field Invoice_Status__c on the Nutshell Deal and appends a deal Activity note with the invoice total, date, and payment terms. Nutshell does not have a native invoicing object.

Estimate Rocket time entries (employee, project, hours, work type) become Nutshell Activity records with a custom Work_Hours__c number field and a Work_Type__c pick-list field. Original timestamps and associated project are linked. Nutshell's time tracking is not native — these custom fields enable manual time reporting.

Estimate Rocket project addresses map to the address fields on the linked Nutshell Company or Person record. Nutshell has no Map View — FlitStack preserves the full address so it can be displayed in external map tools post-migration. Projects with unresolvable addresses are flagged for manual review.