APPENDIX C: INTEGRATION PROJECT PROCESS OVERVIEW
Project Timeline
The duration of your integration project depends on the project size and complexity:
Simple integrations: 3-4 weeks
Standard integrations: 4-6 weeks
Complex integrations: 6-8+ weeks
The timeline includes onboarding, development, testing, and go-live phases.
Onboarding Phase
The onboarding phase prepares your organization and systems for integration development. It follows 4 steps with clear responsibilities for Cloudify and for you.
Step 1: Company Added to Lighthouse
Responsibility: Cloudify
Cloudify will set up your company account in the Lighthouse platform.
You will receive:
An email invitation to join Lighthouse
Access to your integration dashboard
Action required: Accept the invitation and log in to verify access.
Step 2: System Access
Responsibility: You (Client) + Cloudify verifies connection
You will need to provide Cloudify with two types of access to the applications being integrated.
A) Add Apps as Connectors in LighthouseYou will connect your applications to Lighthouse via the Lighthouse dashboard:
How to do this:
Log in to your Lighthouse account
Navigate to "Connections" section
Click "Add Connector" for each application to be integrated
Follow the setup wizard for each app (e.g., HubSpot, Business Central, Xero)
Authorize the connection (typically OAuth or API token)
Verify the connection status shows "Connected"
What this does:
Allows Lighthouse to connect to your applications via API
Enables data to flow between your apps and Lighthouse
Required for the integration to function
Cloudify will:
Provide step-by-step instructions for adding each connector
Guide you through any troubleshooting if connection fails
Verify that connectors are properly configured
B) Provide Front-End Admin Access
In addition to connecting via Lighthouse, Cloudify needs admin access to log in directly to your applications' front-end:
Why this is needed:
To see and understand your data structure
To configure integration settings within your application
To test the integration with sample data before go-live
To troubleshoot issues if they occur
How to provide front-end admin access - Choose one option:
Option 1: Create an Integration User Account (Recommended)
Create a new admin user account in your application
Username: "[YourCompany]-Cloudify-Integration" or similar
Email: Use our support@cloudify.biz company email(for password resets)
Share the login credentials with Cloudify via secure method (email or password manager)
Advantages: Maintains security, can be audited, easy to disable when project ends
Option 2: Share Existing Admin Credentials
Provide Cloudify with an existing admin account username and password
Only recommended if creating a new account is not possible
Note: You can change the password after the project if preferred
Credentials needed for:
Your source system (e.g., HubSpot)
Your target system (e.g., Business Central)
How to share credentials securely:
Email to your Cloudify project contact
Use a secure password sharing tool if preferred
Include: URL, username, password, any 2FA/MFA instructions
Timeline for Step 2: Complete as soon as possible after receiving your Lighthouse invitation. Most clients complete this within 1-3 days.
What Cloudify will do after you complete Step 2:
Verify connector connections are working in Lighthouse
Log in to your applications using provided credentials
Confirm able to access all necessary data and settings
Test read/write permissions needed for the integration
Identify any system configuration needed (Step 3)
Step 3: Possible System Configuration
Responsibility: You (Client)
Before development begins, your systems may need to be configured with specific settings for the integration to work properly.
Examples of configuration that may be needed:
Custom properties or fields in either system
Optional Setup (OSS) or similar feature enablement
Customer posting groups and VAT posting groups (for accounting systems)
Product categories or classifications
Tax rates and payment terms
Multi-entity or company setup (if applicable)
Cloudify will advise: Once we have access to your systems, we'll identify what needs to be configured. We may ask:
"Do you have static rules for customer posting groups, or should we define these during onboarding?"
"Are there specific custom fields needed in HubSpot for this integration?"
"Do you need specific product groupings for the integration?"
Action required: Complete or confirm all required system configuration before the onboarding session.
Timeline: Complete in parallel with or immediately after Step 2. We'll coordinate with you on what needs to be done.
Step 4: Onboarding Session
Responsibility: Both Cloudify and You (Client)
Once Cloudify has access to your systems and any necessary configuration is complete, we'll schedule a 30-minute onboarding session to:
Discuss:
The data structure in your source system (HubSpot, etc.)
The data structure in your target system (Business Central, etc.)
Define unique identifiers for identifying customers, invoice etc across systems
How data will be mapped between systems (customers, invoices, deals, products, etc.)
Any special business logic or rules needed
Finalization of system configuration details
Attendees:
Cloudify development lead
Your IT/technical contact
Business stakeholder familiar with data structures (accounting manager, CRM administrator, etc.)
Preparation required:
Cloudify: Access to both systems to review data structure
You: Have key stakeholders available and ready to discuss business requirements
Outcome: Clear understanding of how the integration will work and any final configuration details needed.
Onboarding Sequence
The onboarding steps must happen in order:
Step 1 (Cloudify): Cloudify creates Lighthouse account → You receive invitation
Step 2 (You + Cloudify): You add connectors and provide front-end credentials → Cloudify verifies connection
Step 3 (You): You configure systems if needed → Coordinated with Cloudify
Step 4 (Both): Once Steps 2-3 complete → Schedule and conduct onboarding session
Total onboarding timeline: Typically 1-2 weeks depending on how quickly you can complete Step 2 and Step 3.
Development Phase
After onboarding is complete, Cloudify's development team builds the integration.
What Happens During Development
Cloudify will:
Map all data fields between your systems
Build workflows that automate data synchronization
Configure how data is transformed, formatted, and validated
Test the integration with sample data
Create a Data Dictionary documenting the implementation
You provide:
Feedback on data mappings and integration behavior
Clarification on business rules or special requirements
Response to technical questions within 5 business days
Data Dictionary
During development, we create a Data Dictionary that documents:
Which data fields are synced
How data is transformed and mapped
Business logic and rules
How errors are handled
The Data Dictionary is project-specific and created based on your actual systems and data.
Development Timeline
Typically 2-4 weeks depending on:
Integration complexity
Number of workflows/data fields
System configuration details
Your responsiveness to questions
Testing and Approval Phase
Once development is complete, you test and approve the integration before go-live.
User Acceptance Testing (UAT)
Cloudify notifies you when the integration is ready for testing. You have 10 business days to:
Test:
Data flows correctly from source to target system
All required data is synchronized
Data is properly formatted and valid
Workflows trigger as expected
Error handling works as described
Verify:
The integration meets your business requirements
The Data Dictionary accurately describes how the integration works
You understand how to use the integration in your business
Provide feedback:
Report any issues or concerns
Request clarification on integration behavior
Data Dictionary Approval
Once you proceed with UAT testing, you are confirming that:
You have reviewed the Data Dictionary
All data mappings are correct
You understand how the integration works
The integration meets your requirements
Testing Timeline
Typically 1 week but can extend up to 2 weeks depending on:
Complexity of testing scenarios
Time to identify and resolve any issues
Your testing availability
Go-Live Phase
Once UAT is complete and you've approved the integration:
Deployment:
The integration is activated in your production environment
Workflows begin automatically processing your live data
Support:
You have access to Lighthouse to monitor the integration
Error alerts are sent via email
Support is available for questions or troubleshooting
The Data Dictionary is your reference for how the integration works
Responsibility Summary
During Onboarding
Cloudify: Step 1 (Lighthouse account)
You: Step 2 (add connectors and provide credentials), Step 3 (configuration)
Both: Step 4 (onboarding session)
During Development
Cloudify: Build integration, create Data Dictionary
You: Review mappings, provide feedback, respond to questions
During Testing
You: Test integration, verify requirements, approve Data Dictionary
Cloudify: Support testing, assist with issue resolution
After Go-Live
You: Monitor integration, resolve data issues
Cloudify: Provide support and maintenance
Timeline Management
Standard Timeline
For a typical integration project:
Week 1: Onboarding (connectors, credentials, configuration, session)
Week 2-4: Development (building integration, creating Data Dictionary)
Week 4-5: UAT (testing and approval)
Week 5: Go-Live
If Timeline Extends
If your project takes longer:
Client delays (slow to add connectors, provide credentials, answer questions, or complete testing):
Timeline extends accordingly
Cloudify is not liable for delays
You are not entitled to refunds for extended timeline
Complexity discoveries (integration is more complex than estimated):
We provide an updated timeline estimate
Additional fees may apply (billed as Additional Services)
You are notified before additional work begins
Changes to Integration Scope
If you request changes after development begins:
Changes are documented
Impact on timeline and cost is assessed
Changes are billed as Additional Services
Support and Reference
After Go-Live
The Data Dictionary serves as:
Reference for how the integration works
Troubleshooting guide if issues occur
Documentation for your team
For help:
Contact: support@cloudify.biz
Access: Log in to Lighthouse dashboard to see integration status
Summary
Your integration project follows a structured process:
Onboarding: Lighthouse setup, add connectors, provide credentials, configuration, onboarding session
Development: Building integration and creating Data Dictionary
Testing: You validate integration meets requirements
Go-Live: Integration begins processing your live data
The entire process typically takes 3-8 weeks depending on project complexity.
Clear responsibilities ensure smooth project execution:
Cloudify handles technical development and integration
You add connectors to Lighthouse, ensure systems are configured and accessible, and provide necessary credentials
Both work together in the onboarding session to define the integration
