Migrate from Planado to Twenty CRM

Planado Jobs are the core record — each job has a client, location, assigned employee, status, and checklist. We map Jobs to Twenty Opportunities. The job name becomes the Opportunity name, the budget or fee becomes the amount, and the job status (new, in progress, completed, cancelled) maps to a value-mapped Opportunity stage. Original job create date preserved as a custom field since Twenty CreatedDate reflects migration time.

Planado Clients that represent individual people (sole proprietors, contacts without a company) migrate as Twenty Person records. The client's display name maps to Person.name, email to Person.email, phone to Person.phone. When a Planado client has no email, we use a placeholder identifier to satisfy Twenty's uniqueness constraint and flag the record for review.

Planado Clients that represent companies or organizations map directly to Twenty Companies. Company name, address, industry, employee count, and annual revenue migrate — industry and employee count require pre-created custom fields in Twenty since these are not standard on the Companies object. Multi-location organizations collapse to one primary Company record with additional addresses stored in a custom field.

Planado Employee records (field workers, technicians, dispatchers) become Twenty Person records. The employee's name, email, phone, and role migrate. Employment status (active, inactive) is stored as a custom field since Twenty has no native employment status field. Employee records must exist in Twenty before Job assignments can reference their OwnerId.

Planado task assignments (which link a specific employee to a specific job on a given date) become Twenty Task records. The task title references the job name, the assigned employee links via the task assignee field, the due date maps from the scheduled date, and the task status maps from the job status. Original schedule timestamp preserved as a custom datetime field.

Planado job checklists contain multi-step structured items with completion status, timestamps, and worker notes. Twenty has no native checklist object, so we serialize each checklist as a Note record attached to the corresponding Opportunity. The Note body contains the full checklist in structured text format (step number, description, status, completion timestamp, worker name) preserving all audit information.

Planado Locations store service site addresses with GPS coordinates. We attach the primary location to the linked Company record as address fields (street, city, state, postal code, country). GPS latitude and longitude are stored as custom fields on the Company record or on the related Task record — Twenty has no native GPS field so these are custom text fields.

Any custom objects defined in Planado migrate to equivalent Twenty custom objects. The custom object schema (field names, types, pick-list values) is exported from Planado and recreated in Twenty via Settings → Data Model before the main import begins. Relationships between custom objects use Twenty's relation field type.

Planado file attachments on jobs (photos, signed forms, inspection reports) re-upload to Twenty as Note attachments. File size limits follow Twenty's attachment constraints. Inline images in Planado notes are downloaded and rehosted as attachments on the corresponding Twenty Opportunity or Task record.

Planado tracks GPS coordinates per job and per employee for route verification. Twenty has no native GPS or routing field. We preserve the last-known coordinates as custom text fields (latitude, longitude) on the Task record, and route history as a custom object (GPS_Waypoints) linked to the Opportunity for teams that need spatial audit trails.