Migrate from Legrand Cloud CRM to Zoho CRM

Legrand Account records export cleanly via the built-in Excel export with standard address, type, and owner fields intact. We ingest Accounts first so that subsequent Contact imports can reference the parent Account linkage during sequence. Zoho's Account API field mapping is straightforward: AccountName, Website, Phone, Industry, BillingStreet, BillingCity, BillingState, BillingPostalCode, and BillingCountry map directly. We use the Account Name as the dedupe key on Zoho import to prevent duplicate Account creation if the same company appears in multiple Legrand exports.

Contacts export with full name, email, phone, role, and parent Account linkage. The Legrand CSV preserves the company relationship; we map it to Zoho's Account_Name lookup field during import sequence. We resolve AccountId by matching the Contact's parent Account name to a Zoho Account record created in the prior phase. Any Contact without a matching Account is flagged in the reconciliation report and held in a staging queue for the customer to resolve before the Contacts phase closes.

Leads arrive through Legrand's dedicated Lead Inbox module. We map Lead source, status, and owner fields to Zoho's equivalent Lead fields. Custom lead fields require manual field-level mapping during the scoping pass because Legrand's per-module custom field schema varies by customer configuration. Owner resolution is by email match against Zoho Users; unresolved owners are held in the reconciliation queue.

Opportunity and Pipeline records export with stage, value, expected close date, and owner assignment. We preserve pipeline stage names as custom text labels if Zoho's default stage vocabulary (Qualification, Needs Analysis, Value Proposition, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost) differs from Legrand's customer-specific stage set. The mapping of Legrand stage to Zoho stage is confirmed with the customer's admin during scoping. Owner resolution follows the same email-match pattern used for Contacts.

Quotes export from Legrand's add-on Quotes module with line items, revision history, and conversion status. We map Quote-to-Order linkage manually since the conversion status does not transfer as a Zoho native field. Line items map to Zoho Quote Line Items with Product Name, Quantity, Unit Price, and Discount preserved. Quotes require Zoho CRM Professional tier or above on the destination; we confirm the customer's Zoho edition during scoping.

Legrand Service Desk tickets map to Zoho Cases. We preserve ticket board, status, age, and custom fields. Internal agent comments do not export via Legrand's standard Excel export; we run a separate comments report before cutover and document it as a supplemental pass with partial coverage. The Asset-to-Ticket linkage migrates as a text reference field. Cases require a Zoho Service Cloud license on the destination; we confirm availability during scoping.

Asset Tracking records export from Legrand's optional add-on with serial number, linked customer, service history, and custom fields. We map these to a Zoho custom module named Assets to preserve the full record structure. The Asset-to-Ticket linkage is preserved as a text reference field since Zoho's native Asset-to-Case linking requires Service Cloud setup. Custom fields are audited individually before migration and created in the destination custom module schema before the Assets import phase.

Legrand Documents export as individual files per record with no folder hierarchy. We bulk-rename files with a ContactID or AccountID prefix for association, then attach them to the matching Zoho record via API. The folder hierarchy is reconstructed manually from the document metadata. This approach differs from Zoho's standard Attachments import because the files arrive in arbitrary order rather than as a named archive, and the Legrand export tool does not generate a manifest linking file to parent record.

Legrand Activities from Google and Outlook integration export as individual text files per activity. We parse each file for timestamp, type (call/email/meeting/task), duration, and body, then map to Zoho Tasks with the activity type preserved in a custom field. Email threads export separately and map to Zoho Notes if they contain narrative content rather than metadata. We separate email bodies from attachments during preprocessing so that attachments are routed to the correct parent record before the main Tasks import phase.

Legrand Campaign records map to Zoho Campaigns with name, type, status, and target member count preserved. Campaign member associations export as a separate sheet; we merge them into Zoho's Campaign Members table using the Contact or Lead ID as the lookup key during the final import phase. Member status (Sent, Responded, Opted Out) migrates to the Zoho Campaign Member Status field.

Legrand per-module custom fields are audited during scoping. We create each custom field in Zoho before migration using the field type that best matches the source data type (text to single-line text, number to numeric field, date to date picker). Zoho permits creating up to 50 custom fields during migration import; if the customer's schema exceeds 50 new fields, we pre-create them in Zoho's module builder before the migration window opens. Field labels are matched to Legrand's naming convention for admin recognition in the new system.