Migrate from Spreadsheet.com to Microsoft Project

Each Spreadsheet.com Workbook maps to one Microsoft Project plan. We preserve the workbook name as the Project name and apply the destination Project calendar (Standard by default, or a custom calendar if the source workbook used non-standard working hours). The Project Start Date is derived from the earliest task Start Date in the source data.

Spreadsheet.com Sheets within a Workbook map to Microsoft Project summary tasks or phases. If the source workbook used a Sheet per project phase or workstream, we create corresponding summary task rows in Project with the Sheet name as the task name and child rows as the detailed tasks. Indentation level in the source Sheet maps to WBS hierarchy.

Each Spreadsheet.com Row maps to a Microsoft Project Task. We map the primary text column to Task Name, date columns to Start and Finish, numeric columns to Duration, and assignment columns to Resources. Row-level comments migrate as Project Notes on the corresponding task. Completed status percentage maps from a progress column to Percent Complete.

Spreadsheet.com date columns (including date picker and formula-computed date cells) normalize to true Excel date serial values before Project import. We run type inference across the source column: if dates are stored as text strings in non-standard format, we parse and reformat to YYYY-MM-DD serial format that the Microsoft Project Import Wizard recognizes. Any column named 'Start', 'Due', 'Deadline', or their equivalents gets mapped to the respective Project field during the Excel template phase.

Spreadsheet.com did not have a native Duration field — teams stored durations as numeric values (often in days) or as formula outputs. We parse the numeric values, infer the unit from column naming (days, hours, weeks) and apply Project duration conversion (days to elapsed days in Project's duration format). Duration columns storing text like '2 weeks' are parsed and converted to Project duration format (e.g., '2 wd' for working days).

Spreadsheet.com allowed free-form text or formula outputs in predecessor columns. We extract task ID references, task name matches, or row index references and convert them to Project predecessor syntax (Task ID with FS/FF/SS/SF type). Circular dependencies are flagged during normalization and escalated to the customer for resolution before import. Lag and lead time parsing requires manual review when source used non-standard notation.

Spreadsheet.com user picker cells store Microsoft 365 email addresses or user display names. We extract the email addresses, resolve them against the destination Project resource list, and map to Resource Names in the import. Unresolved users (not yet provisioned in Project) go to a reconciliation queue. If the source workbook referenced users not in the customer's Microsoft 365 tenant, we flag them for admin review.

Spreadsheet.com column-level type overrides (multi-select checkboxes, choice dropdowns, currency values, numeric fields) map to Microsoft Project custom fields. Multi-select values flatten to Text custom fields with semicolon-separated values; currency columns map to Cost custom fields; numeric columns map to Number or Flag custom fields. We flag any multi-select with more than 10 distinct values for customer review, as Project text custom fields have display limits in the UI.

Spreadsheet.com formula columns (computed cells) cannot migrate as live formulas into Microsoft Project since Project does not have a spreadsheet formula engine per task row. We evaluate formula output at extraction time and write the resulting value as a static custom field. If the formula computes a status indicator (e.g., IF overdue), we document the logic for the customer's admin to implement as a Power Automate rule or a manual flagging process post-migration.

Spreadsheet.com file attachments stored in cell hyperlinks or as linked file references migrate as hyperlinks in the Project task Notes field. File size limits and supported attachment types in Microsoft Project vary between desktop and Project Online. We preserve the original filenames and URLs, and flag any attachments exceeding 50 MB for customer review as Project has no native large-file storage (SharePoint or OneDrive is the recommended attachment path).

Spreadsheet.com Kanban view grouping columns (e.g., 'Status', 'Priority', 'Assignee') do not export as view metadata. We infer grouping intent from row data patterns — if all rows with Status='In Progress' share a common assignee or phase, we document the grouping logic for manual recreation in Project as outline levels or group-by views. True Kanban board rendering in Project requires Project Online with the Board view add-in or a third-party solution; we document this limitation in the view reconstruction plan.

Spreadsheet.com Gantt view configurations are not exportable. We preserve the date range and task duration data so that the Gantt bars render correctly in Microsoft Project after import. Bar styling (color by status, milestone markers) requires manual configuration in Project using the Bar Styles dialog. We deliver a written guide mapping the source view's visual logic to Project Bar Styles settings.

Spreadsheet.com automation rules (triggers, conditions, multi-step actions) were stored server-side without any export mechanism. At shutdown, there was no automation backup. We document every automation identified during discovery — trigger event, condition logic, action sequence, and conditional branching — in a written inventory for the customer's admin to rebuild in Power Automate or as a manual process. Complex multi-step chains require full manual reconstruction.

Spreadsheet.com web form definitions and submission records do not have a migration path to Microsoft Project. Submission rows migrate as task records (see Row -> Task mapping). Conditional form logic, conditional visibility rules, and approval routing do not transfer. We document the form structure and submission schema so the customer can rebuild intake processes using SharePoint Lists with Power Apps forms or Microsoft Forms as the replacement.