How long does a GorillaDesk to HubSpot migration take?

Most GorillaDesk to HubSpot migrations complete in 5–10 business days for datasets under 25,000 records. The extraction phase from GorillaDesk's API runs 1–3 days depending on record volume and API rate-limit handling. HubSpot custom field setup (15–30 properties) takes your admin 1–2 days. Sample migration validation adds 2–3 days. Full cutover with delta pickup runs 1–2 days. Larger setups with 100,000+ records or complex service template hierarchies extend to 3–6 weeks.

Will my GorillaDesk workflows and automations migrate to HubSpot?

No. GorillaDesk automations (job-triggered notifications, route assignments, payment reminders) and workflow logic do not transfer to HubSpot because the automation engines are fundamentally different. HubSpot has a separate Workflows product that must be rebuilt from scratch. We export your GorillaDesk workflow definitions as a reference document listing every active automation, trigger, and action — your HubSpot admin uses this to rebuild them in HubSpot Workflows.

What does a GorillaDesk job become in HubSpot?

A GorillaDesk job maps to a HubSpot ticket. The job ID, status, service type, scheduled date, technician assignment, and materials used are stored as custom properties on the ticket record. Original create timestamps are preserved in a custom datetime field (HubSpot's native CreatedDate reflects migration time). Service history from past GorillaDesk jobs appears as engagement entries on the associated contact timeline, giving your team a complete field service history without leaving the contact record.

Can I migrate GorillaDesk custom objects to HubSpot custom objects?

GorillaDesk does not expose a public custom object API, but it stores service templates (predefined job checklists with frequency settings) that require a HubSpot custom object to preserve. We create a Service_Template__c custom object in HubSpot linked to ticket records via a lookup relationship. Materials used, chemicals applied, and service frequencies become custom properties on both the Service_Template__c object and the ticket. Your admin can create the custom object via HubSpot Settings before migration begins.

What happens to GorillaDesk customer property notes (access codes, gate codes, special instructions)?

Property-level notes from GorillaDesk — gate codes, access instructions, pet locations, lawn conditions, property-specific restrictions — are preserved as custom text fields on the associated HubSpot contact record. We map them to a property_notes__c custom field. When a service technician is assigned to a job in HubSpot (via the ticket owner field), they can view these notes on the contact record from the HubSpot mobile app before arriving on site.

Does the migration affect my GorillaDesk account during the cutover?

No. FlitStack AI uses read-only scoped access to the GorillaDesk API during the migration. Your team continues operating in GorillaDesk normally — scheduling jobs, dispatching technicians, and sending invoices. Any records created or modified during the cutover window are captured in a delta-pickup phase of 24–48 hours so HubSpot reflects GorillaDesk's final state at go-live. GorillaDesk billing continues uninterrupted throughout the migration.

What are the biggest data-loss risks in a GorillaDesk to HubSpot migration?

The primary risk is GorillaDesk's limited API — call recordings, SMS message history, and GPS route data are not accessible via the documented REST API and cannot be migrated automatically. These must be downloaded separately or accepted as non-transferable. The second risk is HubSpot's lack of a native field-service model: job-level data (materials, chemicals, checklists) requires 15–30 custom fields; if your admin doesn't pre-create these, the migration plan flags every unmapped field before data lands.

How does GorillaDesk's invoicing data map to HubSpot deals?

GorillaDesk invoices and payment records (invoice ID, amount, amount paid, payment method, balance due) are stored as custom fields on the corresponding HubSpot deal record. The deal name references the estimate or job number for reconciliation. HubSpot does not have native invoicing — invoice PDFs cannot be natively attached and must be downloaded from GorillaDesk and re-uploaded as files to the deal. If invoicing is a core workflow, HubSpot Payments (Stripe integration) or a third-party invoicing tool must be configured post-migration.

GorillaDesk to HubSpot Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

GorillaDesk organizes field service around jobs, service templates, customers, and technicians — a model built for dispatch, invoicing, and mobile crew management. HubSpot organizes data around contacts, companies, deals, and tickets — a model built for sales pipeline visibility, marketing attribution, and service ticket lifecycle. These data models diverge significantly at the job-record level: GorillaDesk stores work orders with chemicals used, materials consumed, and GPS routes; HubSpot has no native field-service equivalent. We map GorillaDesk customers to HubSpot contacts (and optionally companies), GorillaDesk jobs to HubSpot tickets with custom properties, service templates to HubSpot custom objects, and technician records to HubSpot user accounts with associated contact records. Files and attachments from GorillaDesk are downloaded and re-uploaded to HubSpot Files. We extract data through the GorillaDesk REST API using paginated calls and rate-limit handling (429 response triggers pause-per-retry headers). Workflows, automations, and scheduling logic do not migrate — those are rebuilt in HubSpot Workflows or reported as a manual-rebuild work item in the migration plan.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

GorillaDesk

What's pushing teams away

Office managers consistently note that reporting is underpowered on the Basic plan and that upgrading to Pro is required to access meaningful business analytics, creating a forced upgrade for reporting-heavy users.
Slow app syncing and unreliable offline access affect roughly one in five users, particularly technicians working in areas with inconsistent cell service, where data can fail to save or require manual re-entry.
Route optimization does not account for real-time traffic conditions, so dispatchers must manually adjust routes throughout the day rather than relying on the system to account for delays.
Some customers report that pricing adds up quickly when add-ons for GPS tracking, materials management, and VoIP are factored in, making the effective cost significantly higher than the base tier.

Choosing

HubSpot

What's pulling them in

Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How GorillaDesk objects map to HubSpot

Each row shows how a GorillaDesk object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

GorillaDesk

GorillaDesk Customer

maps to

HubSpot

HubSpot Contact (+ Company)

1:1

Fully supported

We map GorillaDesk customers directly to HubSpot contacts, preserving the customer name, email, phone, address, and property data as contact properties. Property-level details (access codes, service notes, preferred technician) map to custom contact properties in HubSpot so the field context travels with every contact record.

GorillaDesk

GorillaDesk Job

maps to

HubSpot

HubSpot Ticket

1:1

Fully supported

GorillaDesk jobs become HubSpot tickets with the job ID stored as a custom property, job status mapped to ticket pipeline stages (Open, In Progress, Waiting, Resolved), and service type stored as a custom pick-list. Original timestamps and technician assignments are preserved in custom datetime and user-lookup fields.

GorillaDesk

GorillaDesk Estimate

maps to

HubSpot

HubSpot Deal (line items)

1:1

Fully supported

GorillaDesk estimates map to HubSpot deals as the deal record, with line items carrying the estimate's amounts and products. The deal name references the estimate number and customer. Pricing models differ — GorillaDesk's estimate documents are separate from jobs, while HubSpot deals handle the financial record.

GorillaDesk

GorillaDesk Work Order

maps to

HubSpot

HubSpot Ticket Custom Fields

1:1

Fully supported

The work order number from GorillaDesk maps to a custom ticket property (Work_Order_Number__c). Materials used and chemicals applied on site are stored as custom text fields on the ticket. Any attachments on the work order are downloaded and re-uploaded to HubSpot Files associated to the ticket.

GorillaDesk

GorillaDesk Service Template

maps to

HubSpot

HubSpot Custom Object or Ticket Properties

1:1

Fully supported

GorillaDesk service templates define the checklist and scope of recurring jobs — these have no native HubSpot equivalent. We create a HubSpot custom object (Service_Template__c) to store the template name, checklist items, and frequency settings. Ticket records are linked to the appropriate service template record via a lookup relationship.

GorillaDesk

GorillaDesk User / Technician

maps to

HubSpot

HubSpot User (+ Contact record)

1:1

Fully supported

GorillaDesk users and technicians map to HubSpot user accounts, preserving their email, name, and role. We create an associated HubSpot contact record for each technician so their service history and assigned jobs appear on both the HubSpot user profile and the contact timeline.

GorillaDesk

GorillaDesk Notes

maps to

HubSpot

HubSpot Engagement Notes

1:1

Fully supported

GorillaDesk notes on customers and jobs migrate as HubSpot engagement notes, preserving the original note body, creation timestamp, and author. Notes appear in chronological order on the HubSpot contact's timeline under the Engagements section.

GorillaDesk

GorillaDesk Invoice / Payment

maps to

HubSpot

HubSpot Deal Custom Fields

1:1

Fully supported

GorillaDesk invoices and payments (invoice ID, amount paid, payment method, balance due) are stored as custom fields on the associated HubSpot deal record. HubSpot does not have native invoicing — financial summaries are preserved for reporting but must be reconciled against an external invoicing tool.

GorillaDesk

GorillaDesk Service Type

maps to

HubSpot

HubSpot Custom Pick-list Property

1:1

Fully supported

GorillaDesk service type taxonomy (pest control treatments, pool service, cleaning visits, etc.) is preserved by creating a custom pick-list property (Service_Type__c) on the HubSpot ticket. Each GorillaDesk service type value is mapped one-to-one to the HubSpot pick-list to maintain taxonomy continuity.

GorillaDesk

GorillaDesk Job History

maps to

HubSpot

HubSpot Contact Timeline (Engagements)

1:1

Fully supported

Historical job records attached to a GorillaDesk customer migrate as engagement entries on the HubSpot contact timeline, showing job date, service type, technician, and outcome. This gives service reps a complete service history at a glance without leaving the contact record.

GorillaDesk	HubSpot	Compatibility
GorillaDesk Customer	HubSpot Contact (+ Company)1:1	Fully supported
GorillaDesk Job	HubSpot Ticket1:1	Fully supported
GorillaDesk Estimate	HubSpot Deal (line items)1:1	Fully supported
GorillaDesk Work Order	HubSpot Ticket Custom Fields1:1	Fully supported
GorillaDesk Service Template	HubSpot Custom Object or Ticket Properties1:1	Fully supported
GorillaDesk User / Technician	HubSpot User (+ Contact record)1:1	Fully supported
GorillaDesk Notes	HubSpot Engagement Notes1:1	Fully supported
GorillaDesk Invoice / Payment	HubSpot Deal Custom Fields1:1	Fully supported
GorillaDesk Service Type	HubSpot Custom Pick-list Property1:1	Fully supported
GorillaDesk Job History	HubSpot Contact Timeline (Engagements)1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

GorillaDesk gotchas

High

API lacks bulk export and invoice/job endpoints

High

Customer CSV imports require a paid plan and support involvement

Medium

Reporting data may be inaccessible for Basic plan customers

Medium

GPS tracking and materials data are add-on gated

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

GorillaDesk gotchas		HubSpot gotchas
Severity	Issue	Severity	Issue
High	API lacks bulk export and invoice/job endpoints	High	Marketing Contacts billing model is migration-critical
High	Customer CSV imports require a paid plan and support involvement	High	Feature tier gating is not visible until onboarding
Medium	Reporting data may be inaccessible for Basic plan customers	Medium	Mandatory onboarding fees inflate year-one cost
Medium	GPS tracking and materials data are add-on gated	Medium	HubSpot CSV importer cannot migrate engagements or attachments
		Medium	Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

GorillaDesk API lacks bulk export endpoints

GorillaDesk's REST API exposes individual GET endpoints for customers, users, and notes but provides no bulk export or bulk create endpoint. Large datasets require paginated API calls with cursor-based pagination, and the API enforces rate limits that return a 429 response requiring a pause before retrying. For customer bases above 5,000 records, the migration extraction phase may require multi-session scheduling to avoid rate-limit throttling. FlitStack handles this with automated pagination and retry logic that respects the rate_reset header returned with each 429 response.
Field service data has no native HubSpot equivalent

GorillaDesk stores data specific to field operations — materials used on site, chemicals applied, technician GPS routes, service frequency settings, and job-level checklist completion — that have no HubSpot native object or property. These fields must be recreated as custom fields on HubSpot tickets or as HubSpot custom objects. Service templates require a full custom object (Service_Template__c) with lookup relationships to tickets. Before migration, your HubSpot account needs these custom fields and objects created; FlitStack delivers a schema setup plan listing every required custom property and its type so your admin can pre-build the HubSpot side before data lands.
Job scheduling and dispatch logic does not migrate to HubSpot

GorillaDesk's core value is scheduling, route optimization, and mobile dispatch for field crews. HubSpot does not have a native scheduling or dispatch module — the Service Hub includes a meetings tool for appointment booking, not field crew scheduling. GorillaDesk scheduling rules, route configurations, technician calendars, and recurring job templates have no HubSpot equivalent and must be rebuilt using external scheduling tools (Calendly, OnceHub) or a dedicated field service add-on. FlitStack exports scheduling and frequency data as reference CSVs for your team to use when rebuilding scheduling workflows in HubSpot Workflows or a third-party scheduling tool.
GorillaDesk VoIP call history and SMS threads do not carry over natively

GorillaDesk's in-app VoIP calling (powered by Twilio integration) and native SMS threads are logged within the GorillaDesk job and customer context. HubSpot's calling and conversation features are separate products (Sales Hub Professional+ and Service Hub) and do not import call recordings or SMS history from third-party VoIP integrations. Call recordings from GorillaDesk must be downloaded separately and stored externally or re-uploaded as files to the associated HubSpot contact record. SMS message history is not transferable via API and must be communicated to customers that message continuity will reset in HubSpot.
GorillaDesk invoicing model has no HubSpot equivalent

GorillaDesk has native invoicing, payment collection, and invoice status tracking. HubSpot does not have native invoicing — the closest financial construct is a Deal with an amount and custom payment-status fields. GorillaDesk invoices and payments are preserved as custom fields on the associated deal record, but invoice PDFs cannot be natively attached to HubSpot records; they must be downloaded from GorillaDesk and manually re-uploaded to the deal as a file. If invoicing is a core part of your workflow, HubSpot Payments (a Stripe-connected product) or a third-party invoicing integration must be configured separately after migration.

Migration approach

Six steps for a successful GorillaDesk to HubSpot data migration

Plan and extract GorillaDesk data via API

We audit GorillaDesk's accessible API endpoints and export all available records — customers, jobs, work orders, estimates, invoices, service templates, users, and notes. Because GorillaDesk lacks a bulk export endpoint, we use paginated API calls and handle rate limits (429 responses pause per the rate_reset header). Files and attachments are downloaded separately for re-upload to HubSpot. We generate a data inventory summary so you can confirm the scope before migration begins.
Set up HubSpot custom properties and objects

GorillaDesk field service data requires HubSpot custom fields and a custom object to preserve service templates, materials used, chemicals applied, work order numbers, and service frequency. We deliver a schema setup plan listing every required custom property, its type (text, pick-list, datetime, number, user lookup), and the custom object definition for Service_Template__c. Your HubSpot admin creates these before migration so destination fields exist at load time.
Run a sample migration with field-level diff

We run a representative slice of records — typically 100–300 spanning customers, jobs, and estimates — into HubSpot and produce a field-level diff report. This verifies that job status values map correctly to ticket pipeline stages, service types resolve to the custom pick-list, technician emails match HubSpot users, and GorillaDesk timestamps appear in the custom datetime fields. You review the diff before the full migration commits.
Execute full migration with delta-pickup cutover

The full migration runs in dependency order: customers first (to create HubSpot contacts), then jobs linked to contacts, then estimates as deals, then users and technicians as HubSpot user accounts with contact records. A delta-pickup window of 24–48 hours captures any GorillaDesk records modified or created during the cutover window. All operations are logged in an audit trail, and one-click rollback is available if reconciliation detects a field mapping error.
Deliver rebuild reference and post-migration handoff

We deliver a rebuild reference package documenting your GorillaDesk workflow and scheduling logic so your HubSpot admin can reconstruct automations in HubSpot Workflows. GorillaDesk call recordings and SMS history are provided as a downloadable file package. Post-migration, your team runs final validation in HubSpot and FlitStack provides a 30-day reconciliation window for any missed records.

Platform deep dives

Context on both ends of the pair

GorillaDesk

Source

Strengths

Purpose-built for pest control, lawn care, pool service, and cleaning — chemical-usage tracking and route optimization match those industries' compliance and routing needs out of the box
Affordable entry point at $49/month for up to 3 routes lets two-person crews justify the cost from day one
Mobile app reported as reliable in the field — real-time team location tracking, eSignature capture, and payment processing happen on the technician's device
Free onboarding, unlimited training, and a video library shorten time-to-value for owner-operators who often configure the system themselves
AI Agents handle inbound calls, texts, and web inquiries 24/7 to capture leads and book jobs, lifting after-hours coverage for small shops without adding headcount

Weaknesses

API is read-heavy with no bulk export endpoints; jobs and invoices cannot be extracted programmatically, requiring manual CSV work for full data migration.
Reporting dashboard is locked behind the Pro plan upgrade, limiting historical visibility for Basic-tier customers migrating off the platform.
Slow syncing and unreliable offline access frustrate technicians in low-connectivity areas, potentially leaving unsynced job data incomplete at migration time.
GPS tracking, materials usage, and VoIP are separate paid add-ons; the base plan lacks these features that many pest control and pool operators rely on.
No native AI integration as of early 2026, making it less competitive against newer FSM platforms with embedded AI agents.

HubSpot

Destination

Strengths

Genuinely useful free CRM tier with no seat limit on contact records.
All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
Workflow automation triggers across contacts, deals, and tickets with a visual builder.
API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

	GorillaDesk Source	HubSpot Destination
Strengths	Purpose-built for pest control, lawn care, pool service, and cleaning — chemical-usage tracking and route optimization match those industries' compliance and routing needs out of the box Affordable entry point at $49/month for up to 3 routes lets two-person crews justify the cost from day one Mobile app reported as reliable in the field — real-time team location tracking, eSignature capture, and payment processing happen on the technician's device Free onboarding, unlimited training, and a video library shorten time-to-value for owner-operators who often configure the system themselves AI Agents handle inbound calls, texts, and web inquiries 24/7 to capture leads and book jobs, lifting after-hours coverage for small shops without adding headcount	Genuinely useful free CRM tier with no seat limit on contact records. All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration. Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews. Workflow automation triggers across contacts, deals, and tickets with a visual builder. API coverage for all standard objects including custom objects at Enterprise tier.
Weaknesses	API is read-heavy with no bulk export endpoints; jobs and invoices cannot be extracted programmatically, requiring manual CSV work for full data migration. Reporting dashboard is locked behind the Pro plan upgrade, limiting historical visibility for Basic-tier customers migrating off the platform. Slow syncing and unreliable offline access frustrate technicians in low-connectivity areas, potentially leaving unsynced job data incomplete at migration time. GPS tracking, materials usage, and VoIP are separate paid add-ons; the base plan lacks these features that many pest control and pool operators rely on. No native AI integration as of early 2026, making it less competitive against newer FSM platforms with embedded AI agents.	Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×. Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation. Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page. API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing. Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across GorillaDesk and HubSpot.

Object compatibility
B
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
GorillaDesk: Not publicly documented; a 429 response indicates rate limiting and requires exponential backoff.
Data volume sensitivity
B
GorillaDesk doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from GorillaDesk to HubSpot

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

GorillaDesk

HubSpot

How GorillaDesk objects map to HubSpot

What specifically takes care here

Six steps for a successful GorillaDesk to HubSpot data migration

Context on both ends of the pair

How hard is this migration?

Estimate your GorillaDesk to HubSpot migration cost

What are you migrating?

Frequently asked questions about GorillaDesk to HubSpot data migrations

Can't find your answer?

Related migrations to explore

Move from GorillaDesk.
Land in HubSpot, intact.

Migrate from GorillaDesk to HubSpot

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

GorillaDesk

HubSpot

How GorillaDesk objects map to HubSpot

What specifically takes care here

Six steps for a successful GorillaDesk to HubSpot data migration

Context on both ends of the pair

How hard is this migration?

Estimate your GorillaDesk to HubSpot migration cost

Frequently asked questions about GorillaDesk to HubSpot data migrations

Can't find your answer?

How long does a GorillaDesk to HubSpot migration take?

Will my GorillaDesk workflows and automations migrate to HubSpot?

What does a GorillaDesk job become in HubSpot?

Can I migrate GorillaDesk custom objects to HubSpot custom objects?

What happens to GorillaDesk customer property notes (access codes, gate codes, special instructions)?

Does the migration affect my GorillaDesk account during the cutover?

What are the biggest data-loss risks in a GorillaDesk to HubSpot migration?

How does GorillaDesk's invoicing data map to HubSpot deals?

Related migrations to explore

Move from GorillaDesk. Land in HubSpot, intact.

Move from GorillaDesk.
Land in HubSpot, intact.